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; } } }

Best Practice for Fix Version?

SBJ

Hi,

I'm currently processing issues in Jira and I'm working on a story specifically. This story contains mostly just (sub-)tasks and essentially no bugs, considering it is a new project.

There is this field named Fix Version/s and I mostly interpret this as a bug-related field.

However, would it also be considered the norm to also use this for new projects with no bug-type issues? For instance, setting the Fix Version/s to 1.0 for the very first release? Or would it be better to just not insert a value for this field at all, unless facing a bug-type issue?

Accepted answers

Tarun Sapra

Hello @SBJ

FixVersion is a very important Jira field for new & existing projects both. Basically, your whole release management (if done via Jira) depends on this field. In the project admin section, you can release / archive version thus manage your releases. Using this field everyone in the project team is on the same page in terms of release deadlines and previous releases thus this field is critical.

Please read this document - https://confluence.atlassian.com/jira064/managing-versions-720412374.html

And this -https://www.atlassian.com/blog/jira-software/jira-release-management-steps

All comments

Moses Thomas_08kyb0

@You can use issutype for example (Epic,story task, subtask...) and use fix version/s

and add your fix version/s list(1.0, 2,0 and so on) for the field fix version/s

for Bug issue type: we have another system field for version( Affects version/s) you can use it in the bug screen.

I think this is best practice.

Best!

Tarun Sapra

Hello @SBJ

Please read this document - https://confluence.atlassian.com/jira064/managing-versions-720412374.html

And this -https://www.atlassian.com/blog/jira-software/jira-release-management-steps

SBJ

Hello @Tarun Sapra

Thank you for the clarification! I'll apply this approach right away.

SBJ

Thank you for your input; it is much appreciated!

nguyen.hung

I know this field is important, but the name fixVersion does not fit for Agile Epic/Story usecase.

I'm looking forward to be able to rename or use another version field, something like Target version for ex.

Moses Thomas_08kyb0

@nguyen.hungSo you can create a custom field with drop down list of versions , but then this field will not be the same as version(fix version/ affected version) which are system fields. and are linked to Version in JIRA.

spryce_4rnwc5

Totally agree. It's now "Fix Versions" which just makes it more confusing.

Also why Fix? Is everything a bug?

Ephraim Washington Laidley Jr

I think it has more to do with the "Legacy" of the tool, having started as a ticket system originally (like how all the items are "issue types".)

Ultimately, 'Fix Versions' represents "Releases" to help differentiate organize, report and track based on date of release.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-core

jira-core-cloud

fix-version

best-practice