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?
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
@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.
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
Kanban is a popular agile framework suitable for both operations and development teams. It does not matter if you are a support team handling issues reported by customers, an internal service desk te...
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