Welcome to the FogBugz Knowledge Exchange

Question

6

1

we use scrum with monthly sprints and we produce a software release every few sprints. we'd like to assign a case to multiple milestones - one for the software release and one for the sprint. for example a case should be done for release "MyProduct-v2.7" AND for "Sprint #28, July 2010".

we have tried to use tags and custom fields but neither worked very well (for several reasons - like no reports, typos, no pre-defined fields,....).

what could we do to get reports, filtering, easy entering of releases/milestones,.. for our software releases and sprints?

right now we either move cases around between milestones or we duplicate them and assign one to the release and one to the sprint and link them together. a whole lot of work that everyone hates. :(

thanks

edited Dec 9 2010 at 14:17

cdeszaq
2,264●5●14

asked Jun 16 2010 at 21:41

stmax
76●2

Abhishek Bhargava · Answer 1 · 2011-10-05 16:03:37Z UTC

I agree that we should be able to assign multiple milestones to a case. We release different versions of our software to different clients. Often when a bug is fixed, we need to fix it in multiple software versions and therefore need to assign multiple milestones to a case, one corresponding to each software version in which bug was fixed. By assigning multiple milestones to a case we can generate Release Notes corresponding to each software version cleanly. While duplicating a case to assign different milestones is an option, it creates a huge overhead by increasing case volume, managing/resolving/closing multiple cases, assigning parent cases etc.

Ken Morse · Answer 2 · 2010-06-20 01:50:59Z UTC

1

Perhaps you could use Milestone dependencies and make your sprint milestone a dependency of the software milestone -- then just assign the cases to the appropriate sprint milestone.

answered Jun 20 2010 at 1:50

Ken Morse♦
1,687●3●11

i think one problem with that is that a sprint can contain cases for different releases. like sprint #1 contains cases A and B. case A is planned to go into release v1.0 and case B is planned to go into release v1.1. but once the sprint is over you can't tell anymore if case A was implemented for release 1.0 or 1.1.. all you know is that it was implemented during sprint #1. another problem, you couldn't create a filter to show all cases that should be implemented for a certain release.. – stmax Jun 25 2010 at 19:37

Andreas · Answer 3 · 2010-06-21 07:08:42Z UTC

0

May be the usage of filter is a solution. If you add all your sprints of one release to the search field, you should see, all cases that belongs to one release. For example your release consists of three sprints: milestone:"Sprint #28, July 2010" milestone:"Sprint #29, August 2010" milestone:"Sprint #30, September 2010"

answered Jun 21 2010 at 7:08

Andreas
344●7

thanks for your reply. i think this would have the same problem that i explained in the answer to ken right now. the problem is that a sprint can contain cases that are planned to go into different releases. like sprint #28 contains cases A and B. case A should be finished for release 1.0, case B for release 1.1. i couldn't create a filter for release 1.0 by filtering for "Sprint #28" because it would also include the case B, which doesn't go into release 1.0. – stmax Jun 25 2010 at 19:42

Abhishek Bhargava · Answer 4 · 2011-10-12 21:40:09Z UTC

0

But then i am not able to see the release notes in the filter (since release notes field cannot be shown in bug listing)

answered Oct 12 at 21:40

Abhishek Bhargava
1●1

Assign case to multiple releases/milestones?

4 Answers