ScriptRunner Behaviour - "loosing" behaviour when changing issuetype

Mario Rowies August 13, 2021

Hi all,


I've an behaviour for creating issues which sets some field defaults, like project, linked issue, ...

Here a sample working script:

import com.atlassian.jira.component.ComponentAccessor

def issueManager = ComponentAccessor.getIssueManager()
def customFieldManager = ComponentAccessor.getCustomFieldManager()

def contextIssue = issueManager.getIssueObject(getContextIssueId())

getFieldById("issuelinks-linktype").setFormValue("relates to").setReadOnly(true)

getFieldById("summary").setFormValue("some default for description").setReadOnly(false)


We've a button (via script fragment) for creating the new issue from within another issue for a particular project, getting the project id with a serverside context-provider script .

Works, project is the right one, project field is readonly, issuelink fields are readonly and have the right values, creating the issue is possible and the fields are filled right in the new issue, but...

when changing the issuetype (in this "Create issue" screen) everything except summary get's lost - the project field is not readonly anymore (but it is still the right project), the issuelink-fields are not readonly any more, but the worst is the issuelink fields are empty.


Maybe a bug or am I using the behaviours in the wrong way? (scriptrunner version, JIRA server 7.1.10)



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events