[Development] Bug management and jira workflow

Joerg Bornemann joerg.bornemann at digia.com
Tue Jul 23 15:37:07 CEST 2013

On 23/07/2013 15:21, Blasche Alexander wrote:

> I can see where there might be a confusion. However if I have a choice between the double loading of the Fix for Version and a release blocker task then I vote for the FixFor version field. The release blocker task doesn't even come close to a replacement. One of the most common filters is "What's unresolved and assigned to me for the next release?". Fix for is exactly what you need in this case. Also, as long as the task is not closed it can never be mistaken for a "really fixed" case anyway.
> A somewhat better method would be to Split the FixFor field into two fields (e.g. PlannedFor vs FixedIn).

I'm also using the FixFor field for scheduling the issues assigned to 
me. IMO the blocker meta-tasks can be replaced by consequently using the 
FixedFor field, because there already is a logical split:
     FixFor in unresolved issues == PlannedFor
     FixFor in resolved issued == FixedIn



Joerg Bornemann
Digia, Qt

More information about the Development mailing list