Copying values from task to bug tickets

Question

In my project, I have only two types of tickets. One is a task ticket which will act as a parent and another is a bug ticket which will act as a child. When I create a bug ticket and link it to a parent, I want some of the values in particular fields to be copied from the task (parent) ticket to the bug (child) ticket. Can anyone help me with the automation rule for this?

Melvin Vijayakumar · Answer

Hello @Trudy P Claspill

I dont think I have JIRA application administrator because I wasnt able to see the options you have mentioned, so I tried doing the log actions after the trigger.

From the audit log, I can see that the trigger issue is the bug ticket and the destination issue is the task ticket.

The fields that I want to copy are mentioned in the previous reply (screenshot attached).

1. Affected Component Variant & SW version (Field type : Label)

2. Fix Component Variant & SW Version (Field type : Label)

3. Affected Business Unit (Field type : Label)

Trudy P Claspill · Answer

Additionally  what are the fields you want to copy and what are their custom field types?

And can you show us the details of the Edit action in your rule?

Trudy P Claspill · Answer

Hello @Melvin Vijayakumar

Thank you for that additional information.

Are you a Jira Application Administrator? If you click the gear icon in the upper right corner near your avatar do you see options like Spaces, System, an Work Items?

To get the inward and Outward Descriptions for the link type requires Jira App Admin access, which you have if you see the options I mentioned.

If you do see those options, select Work Items. You will get a new list of options in the panel on the left. In that panel click on Issue Linking. That will show the link types available on your Jira instance. Each one will have a Name, and an Inward and Outward Description. We need to know the value for each. Links are "directional" and the Automation rule decides which item is the "source" and which is the "destination based on that.

If you don't have access to that, the in your rule add two Log actions right after the trigger. In one add this text:

Trigger issue: {{issue.key}}

In the other add this:

destination issue: {{destinationIssue.key}}

Then let us know if the "trigger issue" is the Task or the Bug. And confirm that the "destination issue" is the other issue type.