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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

Fields display "Not Available" in transition screen Edited

Jira Issues 2.pngWe have a transition screen where we include fields populated in previous transitions to provide the user some context.

When the user starts the said transition, the screen correctly displays the values  in those fields. 

When the user is done entering the other required fields for the transition and clicks the button to complete the transition, the transition fails and the screen comes back indicating that the previously populated fields are required (and missing) and those fields now display the pre-populated value but this time they have "(Not Available)" 

By the way those 2 fields are required through transition validation.  I've tried both Fields Required (JSU) and Fields Required Validator (JMWE add-on) and both result in the same situation. It looks to me like there is some sort of timeout for validations and that seems to expire before it is able to confirm the 2 fields already have values. 

Umm, I just checked the release notes for scriptrunner for jira 6.18 and they mention a bug fix SRJIRA-4723 - Read-only values are no longer lost when configuring Edit screen fields for user pickers. The fields where my issue occurs are all read-only fields set as such via scriptrunner behaviours. The other issue we have been facing is that some times when users would go to the Edit screen, some of the fields that are read-only get blanked out. However that happens with all kind of picker fields not only user fields. It also happens with the Summary field. 

We will upgrade scriptrunner from 6.17 to 6.19 and see if this persists

0 answers

Suggest an answer

Log in or Sign up to answer

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