How can I auto-populate Components for a defect with the parent story Components values?

[Brian ORourke]

When a defect is created for a story, I'd like the Components for the story to be auto-populated to the Components field for the defect.  Is there a way to do this?

[Trudy Claspill]

Hello @Brian ORourke 

Welcome to the Atlassian community.

You can use an Automation Rule to copy the Components from the from the story to the defect, after the defect is created, if you have some item within the defect that identifies the source story, like a link.

If you want the Components field auto-populated within the Create Work Item screen before the defect has actually been saved into Jira, that would require a third party app. Jira doesn't provide that sort of functionality.

[Joseph Chung Yin]

@Brian ORourke 

Welcome to the community.  You can create automation rule to trigger off from Issue Created event, then find out the parent story issue and save the component value into a local variable.  Afterward in the same automation rule, conduct the edit issue action to set the component field of your defect issue.  All this is done are within the same automation rule setup.

Can you provide more information on how you establish the defect relationship/association to a story in your process?  So, we can further assist you.

I also agreed with @Trudy Claspill statement too.  Hope this also helps.

Best, Joseph