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

Automation for Copying Fields

unknown

Hello Atlassian Community,

I need to find a way to create automation(s) to copy over 2 fields from Issue A to Issue B, C, and D

Scenario

Issue A is blocked by Issue B, C, and D

Issue B blocks Issue A

Issue C blocks Issue A

Issue D blocks Issue A

Issues B, C, and D are cloned by Issue A in a separate automation.

Issues B, C, and D are NOT linked together (I would be okay if they were, but not necessary)

All four issues (A, B, C, and D) are on separate jira-projects

These are all on the same issue type and request type, let's call it "onboarding"

Does anyone have any automation suggestions?

Accepted answers

unknown

Hi all!

Thank you for your quick responses!

Automation wasn't giving me an easy way to reach out to the B, C, D issue fields since they we created by another automation where they were cloned from A.

But, I figured out a way to make it work yesterday by using JQL for Linked Issues.

I basically had to use automation to search for issues with a matching field, link them together, and edit the 2 fields on them

using two branches because Issue A and Issue B didn't need to be linked, but needed fields updated

but Issue A and Issue C, D were okay to be linked and needed fields updated

@_@ makes my head spin, but after 2 days of trial and error, hopefully this is the one that sticks.

All comments

Jerrold - Empyra

Hi @[deleted]

To copy 2 fields from issue A to B,C and D

You can use

Trigger > as per the requirement

branch > linked issues >Type is blocked by

Action > Edit issue Fields > select the field > copy from trigger issue

For example I have selected Assignee and description field

If you provide more information on when you want to copy this field I can help you with the trigger .

Thank you.

Duc Thang TRAN

Hello @[deleted]

If your instance allows automations across multiple projects, you can use an automation like this.

Scheduled and for Due date and Priority field

2024-05-29 09_26_28-Window.png

Otherwise, I can propose another solution, but it will require three automations.

unknown

Hi all!

Thank you for your quick responses!

Automation wasn't giving me an easy way to reach out to the B, C, D issue fields since they we created by another automation where they were cloned from A.

But, I figured out a way to make it work yesterday by using JQL for Linked Issues.

I basically had to use automation to search for issues with a matching field, link them together, and edit the 2 fields on them

using two branches because Issue A and Issue B didn't need to be linked, but needed fields updated

but Issue A and Issue C, D were okay to be linked and needed fields updated

@_@ makes my head spin, but after 2 days of trial and error, hopefully this is the one that sticks.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

automation

jira-service-management-cloud

jira-service-management

linked-issues

jsm

questions