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

Reporting download link options #470

Open
hemashahumich opened this issue Mar 22, 2024 · 4 comments
Open

Reporting download link options #470

hemashahumich opened this issue Mar 22, 2024 · 4 comments
Assignees
Projects

Comments

@hemashahumich
Copy link
Collaborator

We need to determine the most effective way to provide queue-level information to individual queue owners. One option we discussed is to include a reporting link either under the "Manage Queue" page or at the top pulldown option next to the login name top right corner. Additionally, we could consider placing a link in a column preceding or following the status column for each queue. For instance, we could incorporate a download button on the individual queue details page, accessible to anyone with queue management privileges. This would allow for easy access and utilization of the reporting feature.

I will let you decide on the easiest way to implement this feature.

@hemashahumich hemashahumich added this to To Do in 1.10.0 via automation Mar 25, 2024
@hemashahumich hemashahumich changed the title Reporting download link options for Rel 1.10 Reporting download link options Mar 25, 2024
@OscarSong2003
Copy link
Contributor

Hey, I'm a current student in EECS 481 who is looking to contribute. Wondering if I can potentially contribute to this task? Thanks!

@zqian
Copy link
Member

zqian commented Apr 9, 2024

@OscarSong2003 Thanks for your interest. However, this issue may need more efforts and may not be an ideal candidate for your EECS 481 assignment.

Instead, please choose from those open issues with the label Good First Issue

@zqian
Copy link
Member

zqian commented May 20, 2024

Will check again whether this is still needed once #97 is implemented

@zqian zqian moved this from To Do to In Progress in 1.10.0 May 20, 2024
@zqian zqian moved this from In Progress to To Do in 1.10.0 May 20, 2024
@hemashahumich
Copy link
Collaborator Author

Sounds good to me.

@jonespm jonespm moved this from To Do to In Progress in 1.10.0 Jun 3, 2024
@jonespm jonespm moved this from To Do to In Progress in 1.10.0 Jun 3, 2024
@jonespm jonespm moved this from To Do to In Progress in 1.10.0 Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
1.10.0
  
In Progress
Development

No branches or pull requests

4 participants