Is it possible to create a new ticket whenever the custom field gets updated, using Scriptrunner
1 answer
Hi @Sahish
To answer your question, yes, this is doable. You can do this using the Listener.
Below is a sample working code for your reference:-
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.MutableIssue
def issue = event.issue as MutableIssue
def project = issue.projectObject
def summary = 'This is an auto created issue'
def description = 'This is an example'
def issueFactory = ComponentAccessor.issueFactory
def issueManager = ComponentAccessor.issueManager
def loggedInUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def customFieldManager = ComponentAccessor.customFieldManager
def type = customFieldManager.getCustomFieldObjectsByName('New Type').first()
def typeValue = type.getValue(issue).toString()
def issueObject = issueFactory.issue
if (typeValue != 'null') {
issueObject.setProjectObject(project)
issueObject.setSummary(summary)
issueObject.setDescription(description)
issueObject.setIssueTypeId(project.issueTypes.find { it.name == typeValue }.id)
issueObject.setReporter(loggedInUser)
issueManager.createIssueObject(loggedInUser,issueObject)
issueObject.setPriority(issue.priority)
issueManager.updateIssue(loggedInUser,issueObject, EventDispatchOption.DO_NOT_DISPATCH,false)
}
Please note, the sample working code above is not 100% exact to your environment. Hence, you will need to make the required modifications.
Below is a print screen of the Listener configuration:-
Below are a few test print screens:-
1) Sample existing tickets:-
2) Edit a newly created issue. By default, the New Type value will be None as shown in the image below:-
3) Update the New Type list to the issue type you want to create. In the example below, the issue type selected is Task. Once the New Type list is updated, click on the update button.
4) As expected, a new issue of Task type has been created.
5) Open the newly created issue. The issue will have the default Summary, and Description included. Similar to the original issue, i.e. by default, the New Type field will be blank. The field needs to be updated before it can be displayed.
I hope this helps to answer your question. :)
Thank you and Kind Regards,
Ram
Thanks @Ram Kumar Aravindakshan _Adaptavist_ for giving me the solution. When I tried the above code with my requirements, I got an error. Screen shot is attached for reference.
And one more thing I did not mention in the above. Actually If I update the custom field "Affected Variants " in project called "ABC", the issue ticket should create in project called say "XYZ". If I want to create like this, what sort change should I do in the code?
And after creation of issue, is it possible to get some dialog box on screen with the information "New issue ticket created". ?
Hi @Ram Kumar Aravindakshan _Adaptavist_
The code is as follows:
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.MutableIssue
def issue = event.issue as MutableIssue
def project = issue.projectObject
def summary = 'This is an auto created issue'
def description = 'This is issue'
def issueFactory = ComponentAccessor.issueFactory
def issueManager = ComponentAccessor.issueManager
def loggedInUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def customFieldManager = ComponentAccessor.customFieldManager
def type = customFieldManager.getCustomFieldObjectsByName('Affected Variants for issue').first()
def typeValue = type.getValue(issue).toString()
def issueObject = issueFactory.issue
if (typeValue != 'null') {
issueObject.setProjectObject(project)
issueObject.setSummary(summary)
issueObject.setDescription(description)
issueObject.setIssueTypeId(project.issueTypes.find { it.name == typeValue }.id)
issueObject.setReporter(loggedInUser)
issueManager.createIssueObject(loggedInUser,issueObject)
issueObject.setPriority(issue.priority)
issueManager.updateIssue(loggedInUser,issueObject, EventDispatchOption.DO_NOT_DISPATCH,false)
}
Hi @Sahish
The issue is duplicated in the same project in the previous code I provided.
If you intend to create the issue in a different project, you will need to modify the code as shown below:-
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.MutableIssue
//Take issue from source project
def issue = event.issue as MutableIssue
def summary = 'This is an auto created issue'
def description = 'This is an example'
def issueFactory = ComponentAccessor.issueFactory
def issueManager = ComponentAccessor.issueManager
def projectManager = ComponentAccessor.projectManager
def loggedInUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def customFieldManager = ComponentAccessor.customFieldManager
def type = customFieldManager.getCustomFieldObjectsByName('New Type').first()
def typeValue = type.getValue(issue).toString()
//Configure Target Project
def project = projectManager.getProjectByCurrentKey('RL')
def issueObject = issueFactory.issue
if (typeValue != 'null') {
issueObject.setProjectObject(project)
issueObject.setSummary(summary)
issueObject.setDescription(description)
issueObject.setIssueTypeId(project.issueTypes.find { it.name == typeValue }.id)
issueObject.setReporter(loggedInUser)
issueManager.createIssueObject(loggedInUser, issueObject)
issueObject.setPriority(issue.priority)
issueManager.updateIssue(loggedInUser,issueObject, EventDispatchOption.DO_NOT_DISPATCH,false)
}
Please note, this sample working code is not 100% exact to your environment. Hence, you will need to make the required modifications.
In the updated code, when the change is made to the New Type list in the MOCK project, the new issue will be created in the Restrict Links (RL) project.
However, the Listener is configured for only the MOCK project, i.e., only when the New Type list field is updated in the MOCK project will trigger and create a new issue in the RL project and not vice-versa.
Below is the updated listener config:-
If you intend to trigger it from either project, you will need to modify the Listener configuration accordingly.
I hope this helps to answer your question. :)
Thank you and Kind Regards,
Ram
Hello @Ram Kumar Aravindakshan _Adaptavist_
Affected Version for issue is one custom field with Select list having the above options for selecting.
Hope this data help you
Thanks,
Sahish
Hi @Sahish
If you want to set the value based on a Custom Version Picker, you will need to modify the code slightly, as shown below:-
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.project.version.Version
//Take issue from source project
def issue = event.issue as MutableIssue
def summary = 'This is an auto created issue'
def description = 'This is an example'
def issueFactory = ComponentAccessor.issueFactory
def issueManager = ComponentAccessor.issueManager
def projectManager = ComponentAccessor.projectManager
def customFieldManager = ComponentAccessor.customFieldManager
def loggedInUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def sampleVersions = customFieldManager.getCustomFieldObjectsByName('Sample Version').first()
def sampleVersionsValue = issue.getCustomFieldValue(sampleVersions) as ArrayList<Version>
//Configure Target Project
def project = projectManager.getProjectByCurrentKey('RL')
def issueObject = issueFactory.issue
if (sampleVersionsValue.size() > 0) {
issueObject.setProjectObject(project)
issueObject.setIssueType(issue.issueType)
issueObject.setSummary(summary)
issueObject.setDescription(description)
issueObject.setCustomFieldValue(sampleVersions, issue.getCustomFieldValue(sampleVersions) as ArrayList<Version>)
issueObject.setReporter(loggedInUser)
issueManager.createIssueObject(loggedInUser, issueObject)
issueObject.setPriority(issue.priority)
issueManager.updateIssue(loggedInUser,issueObject, EventDispatchOption.DO_NOT_DISPATCH,false)
}
Please note, the sample working code above is not 100% exact to your environment. Hence, you will need to make the required modifications.
You will need to ensure that both the projects have the same versions configured. If not, this will not work as expected.
Below are a few test print screens:-
1) When the Sample Version picker field is updated in the MOCK project, as shown below, a new issue is created in the RL project as shown in the 2nd print screen.
2) The RL Project creates a new issue and updates the Sample Value picker matching the values set in the MOCK Project.
I hope this helps to solve your question. :)
Thank you and Kind Regards,
Ram
Hi @Ram Kumar Aravindakshan _Adaptavist_ ,
We already have two post functions in the workflow for creating one new issue in two different transitions:
This post function in "Implement" transition.
This post function in "Create new issue" transition.
So, Whenever I am changing the status from Analysis to Implement, I will get one popup screen which has Multiple Variants and Affected Variants (dropdown) Custom fields. If I select Affected variants are some abc, efg , so immediately separate two new issue tickets will be created for these affected variants (used post functions to create a ticket over here) and the issue will be in Implementation status.
So now during this status, I found that other affected variants Like klm, xyz also affecting. I updated the ticket with these variants from the edit option on the screen. So now the total variants are abc,efg,klm,xyz. Now I need to get another separate two new issue tickets for the affected variants klm and xyz. This is my requirement.
Is it possible ? Please advice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.