Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Portfolio release field

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?

1 answer

0 votes
Thomas Atlassian Team Feb 12, 2018

Hi @Ricky Aladort,

 

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.

 

Cheers,

Thomas

Hi Thomas,

 

I have similar question as @Ricky Aladort .

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? 

Thomas Atlassian Team Feb 17, 2019

Hi @E K ,

 

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

150 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you