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.

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

Staff Dashboard Metrics: As staff I can see a tile for overdue tasks and click it to render a table of pets with overdue tasks #707

Open
kasugaijin opened this issue May 14, 2024 · 5 comments
Assignees
Labels

Comments

@kasugaijin
Copy link
Collaborator

kasugaijin commented May 14, 2024

On the staff dashboard index page we can add value by showing a quick glance of metrics, and allowing staff to quickly access work that needs to be done.

In this issue, we want to modify one of the existing tiles to show information on Pet Tasks. Specifically, show the total number of tasks that are not complete AND not overdue, and the number of tasks that are overdue, on all pets. The staff should be able to click on each stat in the tile, and using hotwire, we render a table below of Pets for which these tasks belong. For example, if I click 'Overdue', the table is populated with Pets with overdue tasks. Let's create a table that shows the Pet image, name, and a column for the number of tasks. The staff should be able to click this pet name and be redirected to that pet's show page.

This is a rough representation of the requirements (ignore the columns to the right of the pet name, these are irrelevant).
lol

  • On the index action we will want to generate the stats for overdue tasks and incomplete tasks (not overdue) to show in the tile
  • Make two new actions on the staff dashboard controller to handle generating the responses for click the Overdue and Not overdue links in the tile, you will need to get the appropriate data for the table, including Pet image, name, and number of tasks (incomplete and not overdue, or overdue)
  • Add tests to make sure the collections generated for each route contain what we expect
  • The table should be paginated (I'd say 5 rows per page?)

There's a lot happening here, so let me know if you have questions!

@kasugaijin kasugaijin added on hold Further investigation/decision-making is required Ready Make a comment to get assigned. and removed on hold Further investigation/decision-making is required labels May 14, 2024
@sarvaiyanidhi
Copy link
Contributor

Hi @kasugaijin I can take up this issue. Can you please assign it to me?

@jmilljr24 jmilljr24 added Assigned and removed Ready Make a comment to get assigned. labels May 17, 2024
@jmilljr24
Copy link
Collaborator

@sarvaiyanidhi all yours!

@sarvaiyanidhi
Copy link
Contributor

Just a quick update that I will work on this now from this week and will try push asap. sorry for the delay.

@jmilljr24
Copy link
Collaborator

Just a quick update that I will work on this now from this week and will try push asap. sorry for the delay.

No worries @sarvaiyanidhi !! Thank you for the update.

@kasugaijin
Copy link
Collaborator Author

Absolutely no rush!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants