Automation - option to select issues to link on new ticket

[Andrea_Lawrence]

I have 2 projects (A & B) that serve different purposes and are used by different groups.

• Project A - bug work queue with sub-tasks
• Project B - review requests that require approvals

Currently I have the following workflow/automation:

1. ProjA Bug issue transitioned to request Review
2. transition screen appears with text fields
3. user provides text values and clicks "submit"
4. ProjB Review issue created with text fields from transition screen
5. ProjA Bug and all Sub-tasks linked to created ProjB Review issue

The problem I've run into is that a ProjA Bug ticket could be worked on by multiple people and/or require different types of Reviews. To address this, I'm wondering if this is possible at all with automation/transitions/triggers:

1. ProjA Bug issue transitioned to request Review
2. transition screen appears with text fields and list of all sub-tasks for selection
3. user1 provides text values and selects some sub-tasks
4. ProjB Review1 issue created with text fields from transition screen
5. selected ProjA Sub-tasks linked to created ProjB Review issue
6. user2 repeats steps 1-3 for different sub-tasks
7. ProjB Review2 issue created with text fields from transition screen
8. selected ProjA Sub-tasks linked to created ProjB Review2 issue

I've tried to create illustrations of what I'm wanting to accomplish

[Bill Sheboy]

Hi @Andrea_Lawrence 

In your first scenario, how are you selecting/creating the first 4 subtasks?  Knowing that may help provide ideas on alternatives.  Thanks!

Kind regards,
Bill

[Andrea_Lawrence]

The subtasks are created manually based on what the bug ticket is. For example, a bug ticket might be "API key unused for 90 days" and there would be a subtask for each API key that's unused.

• Bug: API key unused for 90 days
  • Sub1: API key unused for 90 days - key001
  • Sub2: API key unused for 90 days - key002
  • Sub3: API key unused for 90 days - key003
  • Sub4: API key unused for 90 days - key004

To further elaborate on how the first scenario (current) works:

• user1 will transition Bug issue on ProjA
• the transition triggers an automation configured on ProjA
• automation creates issue on ProjB
• Bug is linked to ProjB issue as part of creation via link to "issue that triggered this rule"
• Sub tasks are linked to ProjB issue as last part of automation on ProjA Bug issue

[Fernando Eugênio da Silva]

@Andrea_Lawrence 

Jira does not have an Issue Picker field, so you need to make something like this:

1. Create a Short Text Field to be able to add the sub-tasks key from ProjectA to be linked with Review issue from ProjectB
2. Add this field into your 'Transition Screen' and recommend your users to fill this field only with the key of sub-tasks to be associated with the issue review, dividing by coma (,). Like this: KEY-1111, KEY-2222, KEY-3333
3. In your automation rule add the field 'Linked Issues' and include the smartvalue of the short text field created.
   1. Select the link type
   2. Select the smartvalue: {{triggerIssue.customfield_XXXX}} (Field ID of short text field key collector)

Then Jira will automatically read each key and will associate with the target issue the key of each issue placed in the field at the time of the transition.

When the second person goes to create the other review issue in project B, he will probably see the Short Text key Collector field filled with the information from the first time it was run, just change the keys to be linked or you can add it at the end of your rule an Action to clear this field so it will be empty and ready for the next execution

Hope this helps :)

Regards,

Fernando

[Andrea_Lawrence]

I appreciate the guidance but I'm trying to get away from having users manually type issue keys since that would defeat the purpose of what I'm really trying to do with automation. Also, some of these Bug tickets have 20+ Sub-tasks.