• Community
  • Products
  • Jira Core
  • Questions
  • If you have a software development project that includes multiple steps per story (UX, UI, Dev, Test, Documentation...) is it best to create a workflow or sub-tasks?

If you have a software development project that includes multiple steps per story (UX, UI, Dev, Test, Documentation...) is it best to create a workflow or sub-tasks?

If I have my Epics and Stories defined and prioritized in my backlog, what is the best practice around managing the design, definition, development, and testing in terms of using a Workflow and changing the Assignee, vs. creating Sub-Tasks for each step? What are the benefits and drawbacks of using a Workflow to drive a Story's progress, vs. using Sub-Tasks? 

3 answers

1 accepted

1 vote

Although workflows are not a series of linear steps, it's quite likely that your processes are.  Most people who define a workflow will give you something like "New, authorised, in progress, in test, done".  It's the route an issue should take if it all goes well.  In real life, that covers some of them, but a lot of issues will fail tests, not get done, not get authorised, get deprecated, duplicated or passed over,  and so-on, so a workflow should reflect this.

The question you need to think about is how your process should match.

If you have a story process that is ideally linear, so that a Story will go New, UX, UI, Dev, Test, Docs, Released, Done, then yes, do it in the workflow (even if it skips steps or you allow it to go backwards, it's fine).   Equally important is that it is being worked on by one person at a time.  So when it's in Dev, the assignee is the developer, when in Test, it's a Tester, when it's in Docs, it's the most appropriate person (maybe a tech author, or the developer again, or the BA, etc)

But, if your story process could run in parallel and/or have different assignees, then you want to sub-task it.  There's a lot of options, but here's a common pattern:

  • Story has a workflow of New -> Approved -> Design -> Dev -> Testing -> Ready to release -> Done
  • We create subtasks for:
    • UX and UI and don't move out of Design until they're done
    • All the dev items the developers want to break out for different developers to deal with
    • Any defects found in testing
    • Documentation tasks, often one, sometimes many (when docs would benefit from being written by several people - a dev, BA, user etc)
    • A task to represent implementation


There's lots of ways to approach this, but I think getting the linear/parallel model defined is a very early step.

Ignacio Pulgar Community Champion Dec 21, 2016

Good answer.

Thank you! I like that approach. Appreciate the example too.

0 vote
Ignacio Pulgar Community Champion Dec 21, 2016

Interesting question.

Hello

I would say that if your process and team are really mature already, go for it, do your complex workflow and follow it.

But if you are starting with your team and process, make it simple... use a very simple workflow and use subtasks, comments, and links... you can even split stories if you need to separate for different teams or third party teams.

Once you learn and have certain level of confidence with this "more-or-less-manual process" you could fine-tune your workflow for your next iterations.

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published Friday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

56 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot