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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,348
Community Members
 
Community Events
176
Community Groups

Is it better to use a common workflow between tasks and subtasks?

Currently, we use a simplified workflow for sub-tasks which is a different workflow from regular tasks. I think the intention was to simplify things, but it seems to make things more complicated. For example, I have a task where I am debugging something, and one of my subtasks is to send a testcase to a vendor, which is blocked because I am waiting on the vendor to give me details about what kind of testcase they need. Whenever we are waiting on vendor, we need to use the "Pending Vendor" status, because that is something that is tracked by management. The problem is that subtasks do not have a "Pending Vendor" status. I do not want to move the parent task to "Pending Vendor" because I can still make progress on debugging. Only the subtask itself is waiting on vendor, and plus the subtask is stuck in "In Progress" status even though I am not making progress because it is waiting on vendor.

IMO, it is kind of confusing in general to have different workflows for different statuses. I can see where sometimes you would need to do that, but in this case I don't think we have any reason to. The feedback that I got from IT was: "In general it is not our best practice to give sub-tasks complex workflows." and that using a common workflow "adds additional overhead to users." IT is assuming that using a separate workflow for sub-tasks is better in general. I'm wondering if they just have never used subtasks (they have subtask disabled for their jira tickets) because it seems obvious to me that the opposite is be true, that a common workflow is better unless there is a good reason not to.

What do you guys think?

0 comments

Comment

Log in or Sign up to comment