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

Best Practice for Fix Version?

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?

3 answers

1 accepted

1 vote
Answer accepted

Hello @Alain Bressers

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

Hello @Tarun Sapra

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

@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!

Thank you for your input; it is much appreciated!

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.

nguyen.hung@dell.comSo 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.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

494 views 6 0
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you