nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I want to clear the system field value during the clone of the issue

Sahish

Hello People,

Can anyone help me with the code to clear the system field value during the clone of the issue in jira. we are using script runner add-on.

Example : project = ABC and issue type = Report and field = Component/s

During clone I want to clear the System field Component/s value.

Here I am sharing my code. I used listeners for this.

import com.atlassian.jira.component.ComponentAccessor

import com.atlassian.jira.event.type.EventDispatchOption

import com.atlassian.jira.issue.CustomFieldManager

import com.atlassian.jira.issue.MutableIssue

import com.atlassian.jira.issue.fields.CustomField

import com.atlassian.jira.issue.IssueManager

import com.atlassian.jira.issue.link.IssueLink

import com.atlassian.jira.user.ApplicationUser

Long ISSUE_LINK_TYPE_ID = 10005 //Cloning ID//

String ISSUE_TYPE_ID = 10601 //Report ID//

Set issueComponent = issue.getComponent()

IssueLink issueLink = event.getIssueLink()

if (issueLink.getIssueLinkType().getId() != ISSUE_LINK_TYPE_ID) {

return

}

MutableIssue issue = issueLink.getSourceObject()

if (issue.getIssueType().getId() != ISSUE_TYPE_ID) {

return

}

IssueManager issueManager = ComponentAccessor.getIssueManager()

CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()

ApplicationUser loggedInUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()

Long textSystemField = issue.getComponent()

issue.setissueComponent(textSystemField, null)

issueManager.updateIssue(loggedInUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)

Thanks in advance,

Sahish

Accepted answers

Tuncay Senturk _Snapbytes_

Hi @Sahish

You should create an event listener listening "IssueLinkCreatedEvent"

Here is the code that might boost your work

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.issue.link.IssueLink
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.event.type.EventDispatchOption

Long ISSUE_LINK_TYPE_ID = 10005 //Cloning ID//
String ISSUE_TYPE_ID = 10601 //Report ID//

IssueLink issueLink = event.getIssueLink()

if (issueLink.id == ISSUE_LINK_TYPE_ID) {
   return
}

Issue sourceIssue = issueLink.getSourceObject()
Issue clonedIssue = issueLink.getDestinationObject()

if (clonedIssue.getIssueType().getId() != ISSUE_TYPE_ID) {
   return
}

IssueManager issueManager = ComponentAccessor.getIssueManager()
ApplicationUser loggedInUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
MutableIssue missue = (MutableIssue) clonedIssue
missue.setComponent(new ArrayList())
issueManager.updateIssue(loggedInUser, missue, EventDispatchOption.DO_NOT_DISPATCH, false)

I haven't tested the code, but I believe it would be a good start.

All comments

Tuncay Senturk _Snapbytes_

Hi @Sahish

You should create an event listener listening "IssueLinkCreatedEvent"

Here is the code that might boost your work

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.issue.link.IssueLink
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.event.type.EventDispatchOption

Long ISSUE_LINK_TYPE_ID = 10005 //Cloning ID//
String ISSUE_TYPE_ID = 10601 //Report ID//

IssueLink issueLink = event.getIssueLink()

if (issueLink.id == ISSUE_LINK_TYPE_ID) {
   return
}

Issue sourceIssue = issueLink.getSourceObject()
Issue clonedIssue = issueLink.getDestinationObject()

if (clonedIssue.getIssueType().getId() != ISSUE_TYPE_ID) {
   return
}

IssueManager issueManager = ComponentAccessor.getIssueManager()
ApplicationUser loggedInUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
MutableIssue missue = (MutableIssue) clonedIssue
missue.setComponent(new ArrayList())
issueManager.updateIssue(loggedInUser, missue, EventDispatchOption.DO_NOT_DISPATCH, false)

I haven't tested the code, but I believe it would be a good start.

Sahish

Hi @Tuncay Senturk _Snapbytes_ ,

Thanks for the code. When I run this code, it got successful. But still I can see Component/s field in the cloned issue which has not become null. Still I can see the field in the cloned issue.

For us the field is like dropdown, it has so many Component/s to choose. May be this may cause anything for not becoming null ?

Thanks in advance,

Sahish

Tuncay Senturk _Snapbytes_

Yes null might not be the case there.

Instead, you may set an empty array of component.

Sahish

Hi @Tuncay Senturk _Snapbytes_ ,

Could you please help me on the setting empty array of component which shall show "None"?

Thanks in advance,

Sahish

naveen pandu

Hi @Sahish @Tuncay Senturk _Snapbytes_

Iam facing same issue can you please guid me...

Can this work be done in automation

Tuncay Senturk _Snapbytes_

Hi @naveen pandu

Thank you for your message. It is possible to accomplish this through automation as well. However, if you need further details, I suggest posting a new question as this thread has become quite lengthy and may be difficult for community members to follow.

naveen pandu

Hi @Tuncay Senturk _Snapbytes_

Can you please send the automation rule. How to write automation rule please post... Iam facing this issue since last month. Could you please provide the solution

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

clone