Solution to Creating Issues in another project during transition workflow

[Johnae Mills]

I would like the user to have the option of creating a new ticket to link to the ticket they are currently transitioning into a new state, without leaving that transition modal. 

[Mark Segall]

Hi @Johnae Mills and welcome to the community!

You may be able to do something with a marketplace app, but I took this approach in my past:

• Create custom field that triggers automation (more below - e.g. "Spawn Issue" single select with values of "yes/no")
• Create custom fields that serve as duplicates of the standard fields you wish to populate on the new project (e.g. "x Summary","x Description", "x Priority")
• Add these fields to a screen that you will use as the transition screen for the desired transition(s)
• Create automation

AUTOMATION

• TRIGGER: Field Value Changed (Spawn Issue)
• CONDITION: Spawn Issue = Yes
• ACTION: Create Issue
  Creates the new issue and copies the values captured on the transition screen
  
  • Summary: {{issue.x Summary}}
  • Description: {{issue.x Description}}
  • Priority: {{issue.x Priority}}
  • Linked Issues
    • Blocks Trigger Issue
• ACTION: Edit Issue
  Reset the Spawn issue value to No so that users have to explicitly set to Yes again to avoid creating duplicates in the future
  
  • Spawn Issue = No