How do I create three start/create transitions for one Jira space?

[Liza Gonzalez]

I'm creating three team boards within one Jira space for a client. I am having issues with the automation rule that would transition a new Jira work item to the specific team board. But it isn't working because each team board has a different starting stage. I tried to create a Rovo agent but that didn't work. The workflow is below, I drew the yellow lines to show the two additional starting points. This is a Jira cloud software project.

[Ajay _view26_]

Hi @Liza Gonzalez 

This is a pretty common scenario when you have multiple teams sharing a single project but each team needs its own board with a different starting status.

The core issue is that Jira workflows only allow one "Create" transition — the one that fires when an issue is first created. But there are a couple of ways to get this working.

Option 1: Use a shared "Created" status + automation to route

Keep one common initial status (call it "New" or "Created") as the single create transition target. Then set up an automation rule:

• Trigger: Issue created
• Condition: Check a field that identifies the team — this could be a custom field like "Team", or Component, or even the issue's Label.
• Action: Transition the issue to that team's actual starting status.

So if Team A starts at "Design Review", Team B at "Backlog", and Team C at "Triage", the automation reads the team identifier and transitions accordingly. Each board just filters to show issues in its own set of statuses.

Option 2: Separate workflows per issue type

If the three teams work on different issue types (say Team A does Stories, Team B does Bugs, Team C does Tasks), you can map each issue type to its own workflow inside the same workflow scheme. Each workflow gets its own create transition pointing to the right starting status.

This is cleaner if your teams genuinely handle different work types, and it avoids the "bounce through a shared status" step.