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

Copy component from story to linked issue

Hizkeel Khan

Hi,

How can I copy component field from story to linked issue story bug.

I have created a custom field Story Bug. I have story Test 1 that is part of module 1 component. Now when I try story bug, I want this story bug to have the same component which test 1 have.

While creating story bug, I will link the this story to my story bug so the component field should be copied automatically.

Let me know if this is possible.

Accepted answers

Bill Sheboy

Hi @Hizkeel Khan

I am not quite following your exact scenario...It seems you have an issue of one type (e.g. Story), and when creating another issue want to link that to the first issue and copy the Component field.

That should be possible with an automation rule.

Using automation rules requires learning and experimentation. I recommend trying to create the rule, and if you run into challenges the community can help.

To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Hizkeel Khan

I am not quite following your exact scenario...It seems you have an issue of one type (e.g. Story), and when creating another issue want to link that to the first issue and copy the Component field.

That should be possible with an automation rule.

Using automation rules requires learning and experimentation. I recommend trying to create the rule, and if you run into challenges the community can help.

To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

Hizkeel Khan

@Bill Sheboy - I have worked with automation rules but I think I wasn't able to explain it to you properly. Here is the automation rule I have created.

Linked Issues - Components.png

Let me know if this is the right approach?

Hizkeel Khan

Story Bug.png

Story bug link to Story.png

While I'm creating this story bug and I'm linking it to story.

The story has already component field. I want that component field to be copied in the story bug I'm creating.

What I want is whatever the component field story has, linked issue should have the same component field.

I hope I have made it clear now.
@Bill Sheboy
@Nic Brough -Adaptavist-

Bill Sheboy

When you branch to the linked issues, you are editing those linked issues, and not the newly created one.

An alternative is to gather the linked issues using the Lookup Issues action with JQL, and then use their components to set the value:

trigger: issue created
action: re-fetch issue (When using the issue created trigger, the rule can start so quickly that the data is not yet available. Adding the re-fetch issue slows the rule down and reloads the data before proceeding.)
condition: issue type equals Story Bug
lookup issues: use JQL to get the linked issue
advanced compare condition: check if the lookup returned any results
- first value: {{lookupIssues.size|0}}
- condition: equals
- second value: 1
action: edit issue, setting the component to
- {{lookupIssues.first.components}}

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud