Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

2 votes
Answer accepted

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

Hello @Tarun Sapra

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

Like # people like this
3 votes
Moses Thomas Community Leader May 28, 2018

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

Like Keith Mcdowell likes this

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

Also why Fix? Is everything a bug?

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.

We all understand that the names (fixVersion, issue etc) are all from the ticket system.

And we also know that using a custom field is not a satisfactory solution to replace important system fields like fixVersion (as well as other like components, priority)

What I am asking for is an enhancement to rename these fields or give them an alias to show them up more accurately to the cases

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

275 views 8 7
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