Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

whenever linking happens need to concatenate Status of issue, Summary using Automation in JIra cloud

thumuluru_shreya
Contributor
June 5, 2025

Whenever linking happens the content in system field will be update as linked issue(ex: bug)status

Ex: Linking Instance issue to bug issue whenever the linking happens via instance to bug or bug to instance the field name (System) present in instance issue type it is update as concatenation of linked issue Bug ticket status and Bug ticket summary

Ex: "Manufacturing" : ABC-234"

Here manufacturing is Bug ticket status and ABC-234 is Bug ticket summary

for easy understanding we need to concatenate the linked issue status and summary in the field whenever linking happens

 

Can anyone help on this


 

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2025

Hi @thumuluru_shreya 

What problem are you trying to solve by doing this?  That is, "why do this?" 

Knowing that may help the community to offer better suggestions.  Until we know that...

 

What you describe may become a brittle solution; it will require several rules to keep the Summary value accurate:

  1. When an issue is linked, update the summary
  2. When an issue is unlinked, update the summary
  3. When an issue is deleted and was linked, update the summary
  4. When an issue is created with a link, update the summary (This will case will not consistently trigger a rule with only the trigger from #1 above)
  5. When a linked issue changes status, update the summary
  6. When multiple different issues are linked, what goes in the summary?
  7. When there is an Atlassian outage, rules do not necessarily run for all the events that happened during the outage.  And so a scheduled trigger rule may be needed to "catch up" for problems with the updates.
  8. etc.

 

I recommend pausing to explain this need / scenario with your Jira Site Admin to learn what they suggest to help.

 

Kind regards,
Bill

0 votes
arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2025

Hey @thumuluru_shreya 

Create the following automation:
Trigger: Work Item Linked

Action: Edit work-item: YOUR CUSTOM FIELD, Value: {{issue.status.name}} : {{Issue.summary}}

 

Screenshot 2025-06-05 at 13.36.35.png

thumuluru_shreya
Contributor
June 5, 2025

@arielei ,I didnt get output for this logic. This logic where it will work for current work item or destination work item?

As I mentioned earlier I have Instance ticket and bug ticket the link will happen through only instance to bug here the system field is present in instance ticket whenever the link happens between instance and Bug the bug issue status and summary needs to concatenate to the system field which is present in Instance issue type.

Hope you understand my query. Could you please help in this it might be helpful for me

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2025

Hey @thumuluru_shreya 

Yes, no problem.

Trigger: When work item linked

Branch: On linked issue

Edit work item: 

{{issue.issueLinks.inwardIssue.status.name}}: {{issue.issueLinks.inwardIssue.summary}}

The way it works, when you link a Bug - the trigger is set to work on the Bug and so it will look on its linked issue and will copy that fields to it.

You'll just need to set which field you want to update.

Screenshot 2025-06-05 at 17.37.03.png

 

 

 

 

thumuluru_shreya
Contributor
June 5, 2025

@arielei , Thank you so much its working fine.

If you have any knowledge on this could you please help on below question?

I guess this is possible through workflow validation. Can you help in this?

Instance ticket should not be allowed to transition to the "open", "closed", "Manufacturing" workflow status unless the following conditions are met:
"System" field has been populated in instance ticket
"Severity" field has been populated in instance ticket

 

Link to "Bug ticket" is valid in instance ticket
Link to "Task issue" is valid in instance ticket

 

If the fields are not populated and the links which are linked to instance ticket are not valid then it needs to throw an error message.

 

Then only the instance need to move the following transitions.

thumuluru_shreya
Contributor
June 6, 2025

Hi @arielei , as you suggested logic is working fine but I need to fill that the value in field like double quotes " ".

For this,

issue status and summary needs to concatenate to the system field which is present in Instance issue type.

Actual output of a field: Open : Summary of the data

Expected output of field: "Open : Summary of the data"

 

Could you please help in this it might me helpful for me

 

thumuluru_shreya
Contributor
June 10, 2025

Hi @arielei , Could you please tell me for overwritten logic also.

You shared screenshots right for the same scenario I need overwritten logic.

 

Like if I link 2 task issues for the same bug issue. It needs to overwrite and update the recent value it means which you linked recently that task status and summary needs to update in the field.

In that ,value same as earlier I told right summary and status of task issue should be updated in the field whenever linking happens between bug and task.

 

Its an emmergency, Could you please help me in this

thumuluru_shreya
Contributor
June 10, 2025

Hi @arielei , Is there any update. Could you please help in this. We need to submit to our client

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2025

Hey @thumuluru_shreya 

I gave you a solution to your request - i tested in in my domain.

what is your current question?

thumuluru_shreya
Contributor
June 10, 2025

Hi @arielei , I have 2 issues Task and instance

Whenever the instance is linking to task or task is linking to instance there is one field in instance issue

i.e; system serial this field needs to auto update whenever the link happens between 2 issues and the value in the field will update it as task status and task summary to system serial field which is present in instance ticket.-For this you already gave logic and this is for linking.

Requirement:

And the same thing if task is linking to instance more than one time the value needs to overwritten with latest link type.

It means the instance is already linked to task and system serial field is updated.

if one more task is linked to same instance the field value needs to update as lastest link status and summary.

 

Could you please help in this

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2025

Hey @thumuluru_shreya 

Correct me if i'm wrong, your wish is:
1. You have 2 issue types : Task, Instance
2. Under Instance you have a field called: system serial

 

When ever there is a link between them you need the status and summary from the Task work-item to be populated to the system serial field in the Instance work-item.

 

Is this correct?

thumuluru_shreya
Contributor
June 10, 2025

Hi @arielei , Yes correct

 

if its 2 task are linked to same instance it should overwritten

it means latest link i.e; task status and summary needs to take

 

Thanks

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2025

hey @thumuluru_shreya 

Its a bit complicated due to limitations, i'm working on it and will update you.

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2025

Hey @thumuluru_shreya 

Due to IF Else limitations that can not save vars out side of a branch, you will have to split the automations into 2 automations:
1. Instance to Task - where you link a work-item from Instance.

2. Task to Instance - where you link a work-item from Task.

see images:

Instance To Task:
Screenshot 2025-06-10 at 17.54.40.pngScreenshot 2025-06-10 at 17.54.45.png

 

Task To Instance:
Screenshot 2025-06-10 at 17.54.13.pngScreenshot 2025-06-10 at 17.54.22.pngScreenshot 2025-06-10 at 17.54.26.png

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 11, 2025

Hello @thumuluru_shreya 

Did it work for you?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events