Adding issues to release

[Marika Wojtuń]

Hello,

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

[Thomas Schlegel · Accepted solution]

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:

[Marika Wojtuń]

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

[Thomas Schlegel]

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. 

[Marika Wojtuń]

ok, thanks

[Christoph Baumeister]

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]

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.

[Christoph Baumeister]

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

[Thomas Schlegel]

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?

[Christoph Baumeister]

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

[Thomas Schlegel]

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

[Christopher Dennington]

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

[Lynn Squire]

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?

[ofir gutmacher]

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

[Lynn Squire]

Thank you.

[Silvestra Valciukaite]

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

[Happy Buddha]

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 : 

[Samuel Justus]

@Thomas Schlegel 

Hi Thomas - I added Release version history to the screens for my projects, but the release version I created won't show up as an option within the tickets when I'm trying to assign a release version...

 I was trying to go back to my screens to take a screenshot for context, but now I can't seem to get back to where I was when I edited the screens, so sorry :)

[Tad Livingston]

I had this issue too, but the accepted answer wasn't working.

We have a project that would show the field when viewing the issue, but not when creating the issue.  Because of that, we could't edit that field at all.

I had to go into Jira Administration > Issues > Screens > SCREEN NAME > Configure, and add the field "Fixed Version/s" (or) "Affects Version/s", and save it.

Then I was able to change the field in the ticket, as described above.