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

Adding issues to release


I'm a new QA here and I need to add an issue to a release version. I set up a release version but cannot add a single issue to it, and unfortunatelly jiras help is presenting the old way to do it and it does not apply to new jira

2 answers

1 accepted

4 votes
Answer accepted
Thomas Schlegel Community Leader Feb 19, 2018

Hi Marika,

just hover over the field with the mouse and click the pencil:


Then select your previously created version in the drop-down-field:



I don't have permission o edit this field unfortunately.

Thomas Schlegel Community Leader Feb 19, 2018

Ah, then please have a look at the permission scheme of your project. There, have a look at the permission: "Resolve Issues" - this is the one you need to add a fixversion to an issue. 

Hi @Thomas Schlegel! I also have the issue that I cannot change the fix version/s field when viewing an issue. I checked the permissions for "resolve issues" and any user is allowed to that. Any clue where else to look?

Thomas Schlegel Community Leader Feb 20, 2018

Hi @Christoph Baumeister ,

maybe the issue is already closed? You can't change a closed issue unless you change the default behaviour in the workflow state.

@Thomas Schlegel No, it's unresolved and in the backlog still... :(

Thomas Schlegel Community Leader Feb 20, 2018

Are you able to change the version in the edit form? Can you change any other field?

Hava you already created a version in your project?

@Thomas Schlegel Thanks a lot! I fixed it. It was not listed on the edit screen. Added it there - now I can also edit it directly with the pen icon. 

Like # people like this
Thomas Schlegel Community Leader Feb 20, 2018

You're welcome, @Christoph Baumeister - Great you found the problem!

I think 'Release Version' would make more sense than 'Fix Version' as it corresponds to the feature

Like # people like this

how do you handle issues with a release? For example, you release and a bug is found or the user doesn't agree that it is fixed?

@Lynn Squire:
you block/disable the option to connect the bug to a story which has a released version.
So, the question is really how to fix this bug which now is unrelated to a story and has its version to an "unreleased version"?
We , in bezeqint, manage 2 approaches:
1. we have a general EPIC which doesn't have a version and is called: "Regular bugs". you need to link bugs to it if you can't link it to the corresponding story

2. the PMO, makes a new "clone" of the original released story, with an unreleased version. after this story is created, we can re-assign it to a sprint and, of course, link the new bug to it.


eventually, you might have clones of released stories, but we prefer the more common - "Jira is performing a release, so move open stories to the next sprint".

that is the built-in approach.

Hey @Christoph Baumeister how did you add it to the edit screen?

I think what he meant was you can update the fix version in the edit screen. So if you click on edit, you can update the fix version : 


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

342 views 1 3
Join discussion

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