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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,249
Community Members
 
Community Events
176
Community Groups

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

Atlassian Community Events