Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Automation: Assign issue to next unreleased fix version not updating the field

I've got an automation that runs when any issue is marked as Done, and updates the Fix version to the next unreleased version. It has been working well for a few weeks, but it seems to have stopped updating the field about 2 weeks ago

When I check the logs, it says that the automation ran successfully, but then when I look at the issue the fix version is still blank. As a test, I edited the automation to update issues to a specific fix version and that was working.

Any ideas what could have changed that stopped this working?

1 answer

1 accepted

1 vote
Answer accepted
John Funk Community Leader Feb 08, 2021

Hi Robbie,

There is a known bug that has popped up for this.

You can follow here:

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

I believe this has now been fixed and deployed. @Robbie James 

https://codebarrel.atlassian.net/browse/AUT-2141

Yes, I can confirm it appears to be working now, thanks!

Like John Funk likes this

Hi!

This error also affects the server version of the plugin but i see only a fix for the cloud version. Is there a fix for the server coming?

@jbeg

as far as I know this bug affects server version when issue is cloned and we have fix for that ready to be released with 7.2.9.

I haven't observed that edit issue action is affected.

Cheers 

Daniel

yes this is correct. This affected the server version of the plugin in the use case where an issue is cloned and the "next unreleased version" is used.

Glad to hear that this is being fixed with the next release.

kind regards,

Jens

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

How to log work and track time in Jira when a person is part of multiple teams

  The manager’s daily activities include a list of challenges to reach high levels of efficiency for their teams. Part of these challenges is related to how to deal with the worklog systems sin...

85 views 2 1
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