Open Bug 397739 Opened 17 years ago Updated 12 years ago

Enhance dependencies to produce iCalendars showing defined-on-the-fly workflows

Categories

(Bugzilla :: Dependency Views, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: saundersgreg, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 Build Identifier: version 3.0 This is a feature/enhancement request. Like other bug-tracking software, Bugzilla can give me a list of bugs in order of priority. But with, say, ten top-priority bugs in the list, I can't immeidately see which *one* I should work on first. The dependency graph solves that problem by showing me which bug depends on no other, putting my ducks in a row! Thank you very much. Now I want these ducks-in-dependency-row presented output as an iCalendar. This should be possible given that I have also set for each bug: how long it will take to fix the bugs (say, for example, 8 hours each); and given that I will have told bugzilla how many hours I have in a working day, and which hours of the day those working hours are. What I think this feature would require, though, is being able to specify *bug-state* dependency (instead of the current bug dependency that already exists in Bugzilla). For example: I tell bugzilla that bug X will take 16 hours, that bug Y will take 8 hours, and that bug Y depends on bug X; so bugzilla could then produce an iCalendar showing me that I'll be doing bug X today and tomorrow, and bug Y on the day after tomorrow - ie, only after bug X is done, because bug Y depends on bug X. (This assuming I have told bugzilla that I work eight hours/day.) But: let's say I put bug X into the RESOLVED state, would/should I then be able to start working on bug Y? Or would/should I have to wait until the person who opened X gets around to putting it into the CLOSED state? I think it would depend on the nature of the bugs. But if I could specify these bug-state dependencies, then a calendar could be produced (showing a schedule, expected date-of-completion, etc). With such bug-state dependency it would be helpful of have a new state: RESOLVABLE. A bug X would be put automatically into the RESOLVABLE state when all bugs on which it depends moved into the states upon which the bug X depends. "Ok, bug W is ASSIGNED, bug X and Z have been CLOSED, what do we do now?" System says: bug Z is now RESOLVABLE. "Let's go to work." Reproducible: Always Steps to Reproduce: This is a feature/enhancement request. Actual Results: This is a feature/enhancement request.
This is a cool idea! You could kind of do this now with "show as bug list" on the dependency tree. All we'd need to add is a notion of how long a work day is, and the ability to sort by dependency in the bug list, if that's not already possible. As far as sort by dependency goes, that means that elements the furthest down in the tree would be the highest in the list, and then you could specify a second sort order, maybe Importance.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Priority: -- → P3
Hardware: PC → All
Summary: Enforce bug-state dependency to produce iCalendars showing defined-on-the-fly workflows → Enhance dependencies to produce iCalendars showing defined-on-the-fly workflows
You need to log in before you can comment on or make changes to this bug.