The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Working with FixVersions, affectedVersions and Swimlanes based on JQL

Lars Hahus
February 7, 2013

I'm creating stories in a project with multiple FixVersions named after Milestones.
For each milestone theres a swimlane and for each task a fixversion (milestone) to which the story belongs. if stories need futher iterations I put them as affected versions to the milestones they affect.

So for the Swimlane for Milestone 3 i write:

fixVersion = "Milestone 3" OR affectedVersion = "Milestone 3" OR affectedVersion = "Milestone 2"

but the stories created in MS2(fixversion) that affect MS3(affectedversion) won't show.

Should i reconsider how I use MS and versions or is my JQL just off?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 7, 2013

Have you considered have another swimlane? One specifically for MS2(fixversion) that affect MS3(affectedversion)?

Lars Hahus
February 11, 2013

We COULD do that but it doesn't make much sense milestonewise. I'd like for my team to have one milestone to finish and be active in, not several. Easier would be to just switch the FXverson to milestone 3 but i was under the impression that versions and JQL played nicely.... :)