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,363,123
Community Members
 
Community Events
168
Community Groups

Can't create two separate behaviours with server side script on Component/s field

I created  a behaviour with following server side script based on field Component/s and mapped it to my project/issue type and it works as expected.

import com.atlassian.jira.bc.project.component.ProjectComponent
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript
@BaseScript FieldBehaviours behaviours
def desc = getFieldById("description")
def descValue = desc.getValue()

def templateDGDesignComponentDesc = "THIS IS TEMPATE"

def components = getFieldById(getFieldChanged()).getValue() as List<ProjectComponent>

if (getActionName() == "Create" || getActionName() == "Create Issue") {
if (! underlyingIssue?.description) {
if (descValue == "") {
if (components.any {it.name.contains("DG Design")}) {
desc.setFormValue(templateDGDesignComponentDesc)
}
}
}
}

 

However, when I try to create a new behaviour, which I plan to map to a different project, the minute I select field Component/s and click on Server Side Script, the above code appears, if I update the code and save, it overrides the code in my previous behaviour.

 

Can I not have two behaviours for two separate projects with separate server side code based on Component/s field?

 

1 answer

1 accepted

0 votes
Answer accepted

Hi Susan, 

May I know which Scriptrunner version you're currently using?

It seems like related to this bug: SRJIRA-4418 which had been fixed in Scriptrunner 6.5.0.

Thank you so much for your help. You were correct, I upgraded our version of Scriptrunner from 6.2.1-p5 to the latest version 6.21.0 and the issue is now resolved.

Appreciate your guidance.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events