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

Updates to the errata creation UI and process #393

Open
javihernandez opened this issue Nov 25, 2024 · 0 comments
Open

Updates to the errata creation UI and process #393

javihernandez opened this issue Nov 25, 2024 · 0 comments
Assignees

Comments

@javihernandez
Copy link
Member

  • Errata ID:
    • try to find a way to get the next value, if not
    • user needs to manually enter it. Also add a hint in case the ID is already taken - or another approach
  • To avoid mixing errata pkgs from different platforms, use base platform to ensure this doesn't happen - add a platform check when adding builds
  • Remove: version, status as we won't touch them and their values are fixed
  • Remove 'Ref ID' and 'T̀itle' from edit ref form
  • Remove 'SELF' from list of ref type - and ensure it's always there when errata is released
  • Ensure we can add references to other issue tracking software other than bugzilla, such as jira (red hat uses it), github or bugs.almalinux.org
  • Automatically filter out debugsource and debuginfo pkgs when adding a build
  • Reboot suggested:
    • first check if we use it at all
    • if not, we remove it
    • if yes, we compile the list of pkgs that have this set to 'true' and do it automatically - AND keep the ability for users to set the value of reboot suggested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

No branches or pull requests

1 participant