Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

can you move through to another jira project via a status in the workflow

Building a workflow and when a user moves through this workflow one of the options given to them is already a project that has been created. Is there a way when they move to that option it then links/takes them into the other project.

2 answers

1 accepted

1 vote
Answer accepted

No, there's no way to do this (at least, not in a sane way)

Moving an issue is a structural change, it should never never be part of a standard process.  It should only be done while housekeeping, or when someone has genuinely just got the wrong project.  It is never something you do in a workflow.

0 votes

The might be use cases such as HR/onboarding where there is a number of projects (HR, Finance, IT, Facilities etc) where a single status change in one project (hire approved in HR) might create/update issues within some/all of the other projects. To achieve something like this, you could look at a UI based automation (Automation For Jira / A4J) or a lot of scripting in the workflow. 

Both of those options have pros and cons - some to consider (YMMV)

  • A4J
    • Pros
      • exposes the automation to project admins in the UI
    • Cons
      • The A4J triggers can be quite limiting - eg: the trigger "Create issue" will be fired on EVERY issue created in a project - and you then use a conditional IF to scope the action just to a specific issue type. If someone creates 1000 issues (Bug + Task), but the you scope the IF issue type to Bugs, and there's only 50 bugs and 950 Tasks, you'll have 1000 invocations and it's not clear that 95% of those weren't meant to do anything 
  • Workflow
    • Cons
      • The automation logic is only visible to the jira/system admins
      • Often means scripting and/or other plugins
  • General
    • Cons
      • Any automation that relies on a specific state (transition/user/etc) can cause issues. If you have an automation try and transition an issue, and someone then adds a screen to that transition with a required field - the automation will fail unless you adjust the automation to populate the field. With the workflow script approach above, errors like this can stop the initial action being completed, with A4J, automations (by default) are fired a-sync after the initial action, so you at least have more confidence that step 1 work



Suggest an answer

Log in or Sign up to answer