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; } } }

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

thumuluru.shreya

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

Accepted answers

All comments

arielei

Hey @thumuluru.shreya

Create the following automation:
Trigger: Work Item Linked

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

thumuluru.shreya

@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

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

Bill Sheboy

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:

When an issue is linked, update the summary
When an issue is unlinked, update the summary
When an issue is deleted and was linked, update the summary
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)
When a linked issue changes status, update the summary
When multiple different issues are linked, what goes in the summary?
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.
etc.

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

Kind regards,
Bill

thumuluru.shreya

@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.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management