What JIRA field does Portfolio use to calculate releases? And is this a configurable option? For example, if fixed version is the field, can I choose another field in JIRA for releases?
Portfolio uses the fixVersion field that comes with Jira, it is currently not possible to use another field.
I am definitely curious about your situation and use case, feel free to describe it a bit if you're willing to help understand why this configuration would be useful / necessary in your case.
My situation is as follows: we have sprints of 3 weeks and at each sprint we do a release. We also have a milestone release which can contain one or more sprints.
If I define in protfolio a milestone release (say containing 4 sprint releases), then this is added to JIRA as a "release".
But in JIRA, I will also release each sprint, which should have a fixed version for the issues/user stories fixed/completed in that sprint. I can use the milestone release, but that is not perfect because all sprints will have the same fixed version.
How to handle this situation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are looking at both improving how we handle the conceptual difference of milestone/releases, and supporting multiple fixVersion per issues in Portfolio (https://jira.atlassian.com/browse/JPOSERVER-1931).
For now, you could look at not assigning the milestone release to issues, rank it after the last sprint release and set its release start/end date to be after the previous release ended or with a fixed date. You will require to enable the "Show empty releases" on the timeline still.
Hope that helps,
Thomas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this really going to be fixed? Soon? I spent so much time trying to figure out why no issues (at all) were showing in Portfolio and the reason was the lack of the fix version field. Had to dig deep into the internet.
Also, it would be really cool it portfolio didn't depend on releases and versions. Not every team works like that. For example, for us, every sprint is a release, so we don't even configure releases in jira.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.