nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Versioning & releases

Another agile delivery person

Hi,

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?

Comments

Ashkan Malekly_4jfgcl

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.

Another agile delivery person

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps