Fix Version field is cleared during Resolve transition


When I`m moving issue from status "In Progress" to "Resolved" or from "Resolved" to "Closed", field Fix Version is being cleared. I`m using "Agile Simplified Workflow Scheme" with small modifications (some steps and transitions added). I have checked:

  • workflow settings, and there is no conditions, validators or post functions, related to this field
  • security settings - user who is doing this transitions has user and developer role in this project
  • field and screens - in all screens filed Fixed Version is available

On the resolve issue screen, field Fix Version has data, but after clicking "Resolve", field is cleared. In issue history is information, that I have changed status and fix version at the same history entry.

Anyone has any suggestions?



3 answers

0 votes

Check the resolve transition - what post functions do you currently have on it?

Secondly, do you have any listeners defined?


Thanks for quick sugesstions.

About Resolve Transition:

  • Triggers section is empty
  • Conditions section:
    • Only users with Resolve Issues permission can execute this transition.
  • Validators section is empty
  • Post Function section:
    • Set issue status to the linked status of the destination workflow step.
    • Add a comment to an issue if one is entered during a transition.
    • Update change history for an issue and store the issue in the database.
    • Re-index an issue to keep indexes in sync with the database.
    • Fire a Issue Resolved event that can be processed by the listeners.


About Listeners:

  • We have installed Script Runner > section Script Listers is empty.
  • In system info > Listeners we have:
    • Issue Assignment Listener (com.atlassian.jira.event.listeners.history.IssueAssignHistoryListener),
    • Issue Index Listener (, Mail Listener (com.atlassian.jira.event.listeners.mail.MailListener)

Any ideas?



Perfect detail. It rules out everything I was thinking might be a problem :-( The only other thing I can think of is that someone has implemented some javascript (yuck) that clears it out before the commit is complete. Is that a possibility? As you have the script-runner, could you check to see if it has any "behaviours" defined that might affect fix-version?


We have found a couse. One of plugins, probably Big Picture made this change. If affected issues, where FixVersion date was exceeded. Plugin was restarted and problem does not apeears any more.

In Script Runner we do not have any scripts related to this field. Anyway, thanks for your help.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you