Maybe this is just wishful thinking. I am evaluating JIRA, and one of the things people want here is one issue with multiple fix versions, each with their own status/resolution, so you can close an issue in one version, but leave it open in another. Currently in Telelogic Change, we just have two seperate changes.
I can already tell this probably wouldn't work in JIRA, but are their clever ways some of you handle this? From what I see so far you could use linkage, subtasks, I saw a plugin that supported parent child relationships, but am just exploring right now, trying to think of how to make this relationship of issues easier for users.
Hi James, good thing about JIRA is that you can customize the workflow to 'almost' whatever you need. But, in this case I think Jira issues are more meant to be like an issue per version, if you have to do the same change but for other version it's more like it should be on another issue, that way you can have better statistics. Issues grouped by version.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs