How do i update the labels with the linked issue key?

[danish_khatri]

When a customer creates a ticket in Jira Service Desk, a clone gets created in the Jira software project which basically help us to communicate and provide updates to customer, now what i am trying to achieve is to show my Jira software project key in the customer service desk view using label.

For e.g.

ABCs-123 (test ticket) --> created by customer using Jira service desk 

ABC-2456 (test ticket) --> clone created in my Jira software project 

Now in the customer service desk view they should be able to see the clone ticket no i.e., ABC-2456 using label field.

Issue - When the rule is run it shows successfully run but label field is somehow not getting updated, How can i achieve this?

Note: the value you see below is manually updated and not using automation

 

[Trudy Claspill]

Hello @danish_khatri 

What is the Scope of the rule you have created? That information is on the Rule Details page.

When sharing a rule execution Audit Log, please make sure you click on all the ">" characters on the right to reveal all the details of the messages in the log.

Which of the issue creations, ABCs or ABC, are you expecting to trigger the rule?

How are the ABCs and ABC issue related to each other? Do you created an Issue Link between them?

How are you creating the ABC issue. Is that being created by another rule? If so, please provide screen images of that rule also.

The way the rule is written the Edit action is executed against the same issue that triggers the rule.

If the rule is triggered by the ABC issue then the rule has to have some method to identify the ABCs issue. And then the rule has to change its focus to that issue so it can execute the Edit action against it.

Also if these issues are in different projects then the current logic would require that the rule scope be Multiple Projects and name both the ABC and ABC,s project in the scope.

[Bill Sheboy]

Hi @danish_khatri 

For the JSON expression you show, there are a couple of things preventing the update...

• That link smart value is to the outwardIssue object, not just the key
• That smart value is also a list of values, and thus even when there is only one linked issue, a list is provided...which likely will fail to create the lable

Assuming the created work item has one-and-only-one outward link, please try this expression in the JSON:

{{issue.issuelinks.outwardIssue.key.first}}

And as a safety check to prevent problems with other work item creations triggering this rule, you may want to add a smart value condition to confirm that key is in your software project.  This could be done with a text comparison, or if you increase the rule scope, with a JQL or other condition on the actual work item.

Kind regards,
Bill