Bug 1215019
| Summary: | Improve dependency view | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Jason McDonald <jmcdonal> |
| Component: | Dependency Views | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | dcantrell, dwmw2, huiwang, jmcdonal, mtahir, qgong |
| Target Milestone: | 5.0 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-18 05:01:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1298042 | ||
| Bug Blocks: | 1164132, 1173599, 1179554, 1211440 | ||
|
Description
Jason McDonald
2015-04-24 06:54:56 UTC
I would like to see any of the following: 1) The big white space on a BZ page under the Blocks field and to the left of PM Score through Flags would be a nice place to put a dependency graph. 2) I would like the dependency graph to show the bug number, the component name, and the bug state. 3) For RHEL releases, everything that is acked for a release should block the main release bug. That way we could see a dependency graph or tree for the entire release. Everything should have a place in that tree. 4) We should have a needinfo? type flag or state specifically to nag owners of Depends On bugs that we are waiting on. That sort of mail should be able to sort higher in priority that ordinary BZ mail. 5) A bug that moves to CLOSED and is in a dependency tree should notify Blocks components. This has happened before in RHEL and the component Blocked by something that closes fails to notice that and ends up waiting around. 6) Similar to #5, if a bug in a dependency tree moves to a different RHEL release (via flag, not the version field), that should notify Depends On and Blocks components. That's all I have for now. devnote: assess https://github.com/bayoteers/TreeViewPlus (In reply to David Cantrell from comment #1) > I would like to see any of the following: > > 1) The big white space on a BZ page under the Blocks field and to the left > of PM Score through Flags would be a nice place to put a dependency graph. > > 2) I would like the dependency graph to show the bug number, the component > name, and the bug state. > > 3) For RHEL releases, everything that is acked for a release should block > the main release bug. That way we could see a dependency graph or tree for > the entire release. Everything should have a place in that tree. > > 4) We should have a needinfo? type flag or state specifically to nag owners > of Depends On bugs that we are waiting on. That sort of mail should be able > to sort higher in priority that ordinary BZ mail. > > 5) A bug that moves to CLOSED and is in a dependency tree should notify > Blocks components. This has happened before in RHEL and the component > Blocked by something that closes fails to notice that and ends up waiting > around. > > 6) Similar to #5, if a bug in a dependency tree moves to a different RHEL > release (via flag, not the version field), that should notify Depends On and > Blocks components. > > That's all I have for now. Hi, we won't be adding work flow to the dependency viewer, that is what the rules engine is for. We will be going with the default upstream TreeViewPlus and then getting feedback on it when it hits staging. *** Bug 1173599 has been marked as a duplicate of this bug. *** *** Bug 1179554 has been marked as a duplicate of this bug. *** |