The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

what is the difference between a step and a status

Anthony Vizza
November 24, 2015

This question is in reference to Atlassian Documentation: Working in text modewhat is the difference between a step and a status

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 24, 2015

It's a technical thing.

I think of steps as a framework or skeleton to hang everything else on, including the status.  If we got rid of steps, then you'd have to have something else to hang the transitions on, and you'd lose the ability to rename or change status on existing steps, and the xml and execution of the code inside a workflow would become more complex - no big deal for the end users (admins and users), it can be done, but it would be a bit of fiddle.

The important things are

  • You don't need to worry about steps.  They're there, the diagram editor handles them without bothering you much, and as long as your workflow is clear to you, you can mostly ignore them
  • It's a good idea to name steps after the status you'd like them to have.  Not important, but friendly and clear.
  • Your users do not ever see steps.  They only see status.  Steps are for admins only.