Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add moped_user_saved_views table to database #19686

Open
mddilley opened this issue Oct 30, 2024 · 2 comments · May be fixed by cityofaustin/atd-moped#1472
Open

Add moped_user_saved_views table to database #19686

mddilley opened this issue Oct 30, 2024 · 2 comments · May be fixed by cityofaustin/atd-moped#1472
Assignees
@tillyw
Labels
Need: 2-Should Have May be painful to leave out, but the solution is still viable Product: Moped A comprehensive mobility project tracking platform for Austin, Texas Service: Dev Infrastructure and engineering Type: Feature Request for new functionality in an existing application Workgroup: AMD Arterial Management Division Workgroup: TPW Transportation & Public Works Department

Comments

@mddilley
Copy link

mddilley commented Oct 30, 2024 •
edited
Loading

As a user, I want a quick way to see and share a list of Moped projects relevant to a particular project, team, or task. I want to be able to save a view to a table in the Dashboard and add a description so I know what a view shows.

Use cases

  • Give field technicians an easy view of their work without needing to adjust filters and navigate Moped from their iPads
  • Enable all individuals in a workgroup to have easy and immediate (e.g. as soon as they're hired/onboarded) access to key project lists (we could populate default views for users based on their workgroup)

In Scope

  • Database
    • Table contains:
      • id (auto-incremented)
      • description (nullable)
      • url (not nullable)
      • url_json (jsonb of filters for future debugging) Also open to renaming if having json in the name is redundant - url_blob?
      • created_by_user_id (not nullable)
      • updated_by_user_id (not nullable)
      • is_deleted
      • created_at (not nullable)
      • updated_at (not nullable)
        • use existing trigger function (see audit field PRs/issues)
@mddilley mddilley added Workgroup: AMD Arterial Management Division Type: Feature Request for new functionality in an existing application Service: Dev Infrastructure and engineering Need: 2-Should Have May be painful to leave out, but the solution is still viable Product: Moped A comprehensive mobility project tracking platform for Austin, Texas Workgroup: TPW Transportation & Public Works Department labels Oct 30, 2024
@tillyw
Copy link

tillyw commented Oct 30, 2024

what if we called the json field something like filters or query_filters ?

@tillyw tillyw linked a pull request Oct 31, 2024 that will close this issue
Open
4 tasks
@mddilley
Copy link
Author

@tillyw query_filters sounds like a much better fit for the data in the column - let's give it a spin!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tillyw tillyw

Labels
Need: 2-Should Have May be painful to leave out, but the solution is still viable Product: Moped A comprehensive mobility project tracking platform for Austin, Texas Service: Dev Infrastructure and engineering Type: Feature Request for new functionality in an existing application Workgroup: AMD Arterial Management Division Workgroup: TPW Transportation & Public Works Department
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

adds moped_user_saved_views_to_database cityofaustin/atd-moped
2 participants
@tillyw @mddilley