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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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


New to the community & fairly new to Jira, so be gentle! Could someone let me know what the best practises are around versioning of the Jira artefacts please.

My intention is to use Jira portfolio in order to provide visibility of the various teams work we have ongoing. For this, I understand that I have to use the FixVersion field.

What is the best practise here? We have a fairly standard portfolio heirarchy of Themes, initiative, Epics, stories, subtasks etc.

Should say Themes have FixVersions, and should these be all the Fixversion of the various Epics, Epics just contain one FixVersion and all its children stories have the same FixVersion of the Epic?

Sorry, bit of a ramble, but wondering if there is a best practise here, or perhaps there are some guidelines somewhere?






1 answer

Hello @Another agile delivery person 

At first wellcom to community and wellcom to Jira. you have very good idea nad this way is best and what you say about portfolio exactly correct. 

Ok, but still not sure here


We have a number of Epics that each refer to subcomponents of the overall product release.

I have versioned all the Epics with the same version number let just say is called product_release_1.0


The stories under each of the Epic are versioned by their sub component name, so lets say we have three epics each have three stories under them

Epic1 -> versioned (product_release_1.0)

    Story1 - > versioned (sub_component_1

    Story2- > versioned (sub_component_1

    Story3- > versioned (sub_component_1

Epic2 -> versioned (product_release_1.0)

    Story1- > versioned (sub_component_2

    Story2- > versioned (sub_component_2

    Story3- > versioned (sub_component_2

Epic3 - > versioned (product_release_1.0)

    Story1- > versioned (sub_component_3

    Story2- > versioned (sub_component_3

    Story3- > versioned (sub_component_3


I then use portfolio in order to track the progress on the subcomponent development and the overall product release.

Does this sound like a sensible approach, you could of course say look at portfolio and see if it looks sensible, unfortunately the way the team have been working i.e. unpointed story points, stories being bumped over many iterations, lack of dependencies, no version labels, have all made portfolio look a bit of a mess.

Suggest an answer

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

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,555 views 25 18
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