vote up -1 vote down
star
1

Feature: - the ability to specify that all Sub-cases of a Parent Case share comments, emails and release notes. Effectively... the comments, correspondence, release notes (perhaps other attributes) are maintained in the Parent case but are seen identically and editable in all Cases of the family.

Use Cases:

  • users estimate their time and book time against individual cases, but any comments or correspondence added to those cases are grouped together

  • regardless of projects or milestones set in the sub cases, the customer facing release notes belong to the Parent case, its project and Milestone.

  • anyone interested in the full history of all the cases in the family can view easily in the Case they are primarily interested in

  • the feature is optional... the configuration goes with all the Cases in the "Family" or none of them

Value Added:

  • the benefits of improving time estimates by creating sub-cases for every role no longer need to be weighed against the disadvantage of multiple cases containing important, related content
flag
I just learned that FogBugz 7 has a new way to generate release notes, and that several Milestones can be grouped together easily, so Release Notes may not be required as one of the group of "Family" attributes. – PJM Nov 12 at 20:47
Along these lines, I notice in the Online Documentation "In the grid view, the estimate of a parent case is displayed as a sum of its own estimate and all subcase estimates." Which is a great feature that would work well with my feature request. The Estimates are already "collected" by the Parent case, just as I am suggesting for the comments. – PJM Nov 16 at 15:08

2 Answers

vote up 1 vote down

You can easily use the "group edit" functionality to tag or categorize a hierarchy or sub-hierarchy of cases. Forcing attributes of the parent case upon child cases seems a bit too assertive for FogBugz's flexible style of handling case data.

link|flag
I don't think that is possible with email, is it? Also, the group edit functionality is accessible from the case list - used mostly by someone in a project management role. Developers don't work with lists of cases as much as edit cases individually. What I'm asking for in this feature is a way for someone in a planning role to say it's important for the comments in this group of related cases to be seen as a thread - and to be able to achieve that in a way that does not interfere with a developers role of read a case to learn the issue, add comments to case as work progresses – PJM Jan 11 at 15:30
I personally believe that from a usability standpoint, a feature like this would confuse users more than help them. Merging all the comments from multiple cases would take all those "conversations" out of their natural threads and jumble them together. It would be hard to follow discussions and decision-making in the case. – adambox Feb 18 at 20:41
vote up 0 vote down

It would be nice if sub-case inherited the Tags and Category of the parent case.

or if there was an option to chose settings (by user and/or by project) what fields a sub-case should inherit from its parent case (this would be useful especially for custom columns)

link|flag
Quick-add should use the category of the parent case. If it's not and you're running the latest version of FogBugz, please let us know. For tags, we do have a case open (see fogbugz.stackexchange.com/questions/2077) – adambox Feb 18 at 20:57

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.