Copying values from task to bug tickets

[Melvin Vijayakumar]

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?

[Trudy Claspill]

Hello @Melvin Vijayakumar 

Welcome to the Atlassian community.

If I understand correctly the rule you want is:

WHEN a Bug is linked to a Task

THEN copy data from the Task to the Bug

If that is correct, I have some questions for you.

1. Do you use more than one link type to linked these issue?
2. What link type do you use? What are the Outward and Inward Descriptions for the link type(s) used?
3. What would you want to happen if the Bug was unlinked from the Task?
4. What would you want to happen if a Bug already linked to a Task was linked to a second Task?
5. What do you want to happen if the Bug already has data in the specified fields?

Lastly, have you tried to create this rule? Show us what you have and tell us what part you are struggling to figure out, or how the rule is not working as you expect or intend.

[Melvin Vijayakumar]

Hello @Trudy Claspill,
Thanks for your immediate response. Your understanding is correct. When a bug is linked to a task, then copy data from the task to the bug. 

Please find my answers for the below questions.

1. Do you use more than one link type to linked these issue?
   Ans : Currently I'm using only one link type. The bug is linked as a child of the task ticket.
2. What link type do you use? What are the Outward and Inward Descriptions for the link type(s) used?
   Ans : I use child/parent link types to link the tickets based on the type (task/bug). The second part of the question is unclear to me but what i can say from my understanding is that, the task is always a parent ticket and bug is always a child ticket to the parent ticket. A bug ticket can be a child of multiple parent tickets.
3. What would you want to happen if the Bug was unlinked from the Task?
   Ans : If the bug was unlinked from the task then the fields which were copied from that task alone should be removed from the bug ticket.
4. What would you want to happen if a Bug already linked to a Task was linked to a second Task?
   Ans : If the bug was linked to multiple tasks then the values from all the task tickets should be taken and append in the specified fields of the bug ticket.
5. What do you want to happen if the Bug already has data in the specified fields?
   Ans : If the bug already has data in the specified fields, then the values from the task ticket should be appended to the existing values.

I have just been trying to create this rule with the limited knowledge i have and with the help of Rovo AI assistant. Since i have been trying to do trial and error I have not implemented the rule in full. Please find the screenshot attached. As of now, the values from the task ticket are not copied to the bug ticket when i link a bug to the task ticket.

[Trudy Claspill]

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.

[Trudy Claspill]

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?

[Melvin Vijayakumar]

Hello @Trudy 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)