Cloning a specific child issue to an Epic in another project

[Luz Pereyra]

Hi! I am working on a change in a automation, and I would like some advise on how to create a child work item in another project before I start testing.

Following up @Bill Sheboy questions, I add below some context: 

Jira version

• Jira edition: Jira Service Management Cloud
  
  

Project type

• Project type: Team-managed (IT HelpDesk)
  
  

Automation Rule

When an Employee onboarding request is created, we keep a parent request and generate child sub-tasks for each selected application to provision.

• Trigger: Work item created
  
  
• Condition: Issue Type = Employee onboarding
  
  
• Action: Lookup objects (From Staff)
  
  
• Branch: For each Smart value APPLICATION
  
  • Log: Creating sub-task for Application:  Employee Key: Issue custom field.  
    
    
  • Action: Create a new Sub-task in IT HelpDesk (uses the lookup values)
    
    
  • Log: Request participants, application system owners and admins. 

What I would like to add

Within the same branch, only when the application is a specific one, create a work item in another project and attach it to a specific Epic. I understand sub-tasks cannot be children of an Epic.  For reliability (request type/approvals/custom fields), is Create issue preferred over Clone issue when creating the cross-project item and attaching it to the Epic?.

Not sure how to go about this.

Thanks for the help! 

Kind regards, 

L

[Bill Sheboy · Accepted solution]

Hi @Luz Pereyra -- Welcome to the Atlassian Community!

You seem to be asking a question related to an automation rule.  If so...

Context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Kind Regards,
Bill

[Luz Pereyra]

Hi @Bill Sheboy I have updated the question with some context! I really appreciate the help! :)

[Bill Sheboy]

@Luz Pereyra -- Thanks for the additional details, and...I recommend not marking the question as "answered" until it is solved.  That will help other community members join in to offer suggestions.

First your question about using Create Work Item versus Clone Work Item: that depends upon what you need to do.  The clone one helps make it easier to copy some data, so use that when needed.

Regarding the work item types, you are correct that Subtasks cannot be children of an Epic.

Getting back to your original question, how would describe the steps involved as that may help clarify the rule steps?

For example, are you trying to create two different work items, where one is conditional based upon the Application?  If so, the steps inside the branch could add more steps at the end, shown in bold below

• ...
• advanced branch: using the variable application
  • action: write to the audit log
  • action: create work item, for the Subtask
  • action: write to the audit log
  • smart value condition: to check the value of {{application}}
  • action: create the work item in the desired project

This will flow in the order of the steps as each application value is branched over.