Feature #8195
closedRepoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment
Description
As a user, repoclosure should be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment
Updated by Walden Raines about 10 years ago
- Blocks Tracker #8176: Errata Management Incremental Updates added
Updated by Walden Raines about 10 years ago
- Blocks deleted (Tracker #8176: Errata Management Incremental Updates)
Updated by Walden Raines about 10 years ago
- Related to Tracker #8176: Errata Management Incremental Updates added
Updated by Walden Raines about 10 years ago
- Subject changed from Repoclosure should be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment to Repoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment
- Translation missing: en.field_story_points set to 8.0
Could be ran as a separate report and is useful for filters as well.
This is optional for the Errrata Management Incremental Updates.
Updated by Pat Riehecky over 9 years ago
When creating a filter set, tracing the dependencies by hand can be very frustrating to end users.
Updated by Walden Raines about 9 years ago
- Related to deleted (Tracker #8176: Errata Management Incremental Updates)
Updated by Walden Raines about 9 years ago
- Blocks Tracker #8324: Errata Management Future added
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release set to 114
Updated by John Mitsch over 5 years ago
- Status changed from New to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.