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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups


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

0 votes

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

Atlassian Community Events