Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Setting up stations in a flow

I have been challenged by a project that needs stations set up for the processing of tickets.  Each stations will have specific statuses and some stations can move back and forth.  Can anyone supply steps or information on this set up please?

2 answers

There is no way to do this as a workflow - Jira's workflows are flat, not layered, there's nothing that could do your "stations".

But you can build something that will enable reporting and even boards for different stations.

First, build a workflow from all of your status.   The "stations" won't matter until you start thinking about how you want to move between them.  I suspect that you might want to set it up so that:

  • Most status can only be transitioned to other status that are in the same station
  • Your two to-do status (you'll need a different name for one of them), and "ready for requirements" should have an "all" transition - "all status can transition to this".  That enables your "move between stations at any point"

Second, to get the "station" reporting and boards, create a "Station" custom field.   I would suggest a select list, with the three station names as options.  Do NOT put it on any create, edit, or transition screens, only view if you want people to see it in with the other fields.

Third write an Automation that works out as "when status changes change the station field to the appropriate one for the new status" (you can reduce execution numbers and logs by limiting it to only the transitions that change the station).

This gives you search and reporting on your stations, and, as a bonus, means you can create boards based on "station = xyz".  I mention this because you need to be a little careful with board columns, especially if you're using Scrum boards.

In Scrum boards:  the "build" board, you can just map all the build status and leave the other two stations out if you want.  But the "requirements gathering" board should map all the build status into its done column, and the "initial design" needs to have all the other station's status in its done column.

In Kanban boards: you will need to do the same mapping, but also edit the "sub-filters" for them so that they don't work off "version" (unless you're educate design/require to never "release" from their boards).

0 votes
Dave Mathijs Community Leader Dec 05, 2022

Hi @Trena Norcia can you define what you meen by 'stations'? Are you talking about gates of phases of a project?

I am using stations as I lack a better word.  We need  basically have points where a ticket will stop in for status changes.  Tickets should be able to move between stations.  Kinda  like a train, stops at stops and several things can happen and it moves on, but can go back to the stop.

Please tell me if this is possible an how to make it happen. This is an urgent need for us

I want to run the "stations" and statuses that we should have within each "station" in JIRA.  Does this make sense to you?

We have 3 main stations: Initial Design, Requirements, Build

Here are the different statuses within each I will need

Initial Design

  • To do
  • Design
  • Ready for Tech Review
  • Ready for Requirements

Requirements Gathering

  • Ready for Requirements
  • Defining Requirements
  • Ready for Tech Review
  • Technical Approval
  • Pending Client Approval --> To do 


  • To do
  • In development
  • Ready to Deploy
  • Ready for QA
  • QA in progress
  • QA Pass
  • QA Fail
  • Done

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events