Next Unreleased version doesn't work for edit issue field fixVersion

[Kostiantyn Teneta]

When I am trying to set the fix version explicitly it works as expected, but when I use the "next unreleased" or "last released" version - nothing happens. And even more, if I have already something in that field it changes it to an empty field.
What am I doing wrong?

[John Funk · Accepted solution]

Hi Kostiantyn - Welcome to the Atlassian Community!

Can you share the Audit Log where it is not working?

Are you sure you have an unreleased version on the project which has dates attached to it? 

[Bill Sheboy]

Hi @Kostiantyn Teneta 

In addition to John's questions, would you please add a screen image of your releases (version) page?

Thanks,
Bill

[John Funk]

Unfortunately, I have been able to duplicate the problem. It fires, gives no error, says it worked, but it still doesn't have a value.  :-(

[Kostiantyn Teneta]

@John Funk yeah, it shows that everything is fine, and the log is empty.

[Kostiantyn Teneta]

upd it works the same way in paid and in free jira versions

[Bill Sheboy]

Oops... looks like this is version related:

• Tried a rule with Affects Version field: same symptom
• Tried a rule with Last Released Version: same symptom
• Called the REST API manually and all versions are still returned, including the correct attributes values for released

@Kostiantyn Teneta did you submit a support ticket on this?  Thanks!

[Kostiantyn Teneta]

@Bill Sheboy Unfortunately, I didn't. I am not an owner of the paid Jira version.

Are you able to do that?

Br,

Kostiantyn

[Bill Sheboy]

Hi!  If you are on a paid instance, your site admin can submit the issue here:

https://support.atlassian.com/contact/#/

[fujiwara manabu]

Hi!

Issue was created related this problem.

https://jira.atlassian.com/browse/JRACLOUD-75982

[Kostiantyn Teneta]

@fujiwara manabu thanks a lot!

[John Funk]

Thanks for sharing that - I have voted for it and am watching it. 

[Kostiantyn Teneta]

It already should be fixed.