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

WIP - RELENG-941: Display used Releases, unless unused requested #2562

Conversation

gabrielBusta
Copy link
Member

@gabrielBusta gabrielBusta commented Jun 17, 2022

Issue #2561 - Consider only displaying "used" Releases, unless unused requested

@gabrielBusta gabrielBusta added the frontend ui issues label Jun 17, 2022
@gabrielBusta gabrielBusta requested a review from jcristau as a code owner June 17, 2022 18:45
@gabrielBusta gabrielBusta self-assigned this Jun 17, 2022
@escapewindow
Copy link
Contributor

As mentioned in the jira ticket, we often add a new release and need to be able to view it/reference it in a rule change. So rather than hiding all unused, I’d prefer if we hid unused-and-older-than-time-threshold.

@gabrielBusta gabrielBusta changed the title RELENG-941: Display used Releases, unless unused requested WIP - RELENG-941: Display used Releases, unless unused requested Jun 17, 2022
@gabrielBusta
Copy link
Member Author

gabrielBusta commented Jun 17, 2022

This is a toggle switch that hides/un-hides the unused releases. If we need to look at the unused releases we can toggle it. Right now it defaults to hiding the unused releases.

@escapewindow
Copy link
Contributor

Is it difficult to have the toggle hide/show unused-but-older-than, say, 6 months releases?

@gabrielBusta
Copy link
Member Author

gabrielBusta commented Jun 17, 2022

No, it would be straight forward. The toggle could hide/show unused releases older than 6 months.

@gbrownmozilla
Copy link
Contributor

+1 for hiding unused-and-older-than-X; the newly added release is an important consideration. I would think X=a few days would be fine, but 6 months is okay with me too.

@gabrielBusta
Copy link
Member Author

I may have spoken too soon. It doesn't look like the Balrog releases keep track of the date they are created. The ShipIt releases are the ones with a "created" timestamp.

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

Successfully merging this pull request may close these issues.

3 participants