Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Jira 8.0 upgrade breaks behaviour scripts - is this happening to anyone else?

Hi -- we are in the process of testing the Jira 8.0 upgrade on a staging environment and I've noticed that a few of the behaviour scripts no longer work.  Initially they had a warning on the script to change getCustomFieldObjectByName to getCustomFieldObjectsByName -- once you do this other parts of the script break, see below.  (The script doesn't work if you leave the warning in place either)

 

These are the imports on the script:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.customfields.manager.OptionsManager

1. getRelevantConfig(getIssueContext()) -- no longer works with the error message: cannot find matching method...please check if the declared type is correct and if the method exists. 

2. ComponentAccessor.getOptionsManager().getOptions(customfield) -- no longer works with the error message: please check if the declared type is correct and if the method exists.  

3. it.value -- no longer works with an error of no such property: value for class: java.lang.Object

4. it.optionId.toString() -- no longer works with an error of no such property: optionId for class: java.lang.Object

 

The behaviour script works on Jira 7.6.13

1 answer

1 accepted

0 votes
Answer accepted

Figured it out -- The fix was to add .first()

 

customFieldObject.first().getRelevantConfig(getIssueContext())

Hello @BSte

Your own solution helped me too. I got the same issue and "first()" solved it.

Do you mind to share the final line to actually update the issue? I assume the syntax also changed since Jira 8.0.

Best

Kristian

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

78 views 0 4
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