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's the difference between workflow and simple workflow

Kristin Bitler
Contributor
November 2, 2015

There doesn't seem to be any information that helps distinguish the difference between a workflow and a simplified workflow. 

I want to add a post function to a workflow for a simple time tracking Project (not using Agile or Kanban) and am unsure if the auto-assign to issue creator isn't working because it's a simple workflow (I can't tell) or how I create a non-simple workflow so I can get this post function to function.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
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 2, 2015

A simplified workflow should be highlighted to you by the name of it.  You should not add post functions or anything else to them, as they can break, and it is possible (and easy) for project owners to scrub your changes.

 

A non-simplified workflow just means using a different workflow scheme.  Although I often use simplified workflows as a base for building non-simplified ones, I always change the name to make it clear.