You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have a number of tickets running in a sprint - and some require design work, and some dont. What would be the best way of making that visible to the design team and developers? I was thinking the use of labels and then having a quick filter for 'design required' and 'design completed & attached' - however this would mean the label needs to be updated each time the design team has completed the design.
Welcome to the Atlassian Community!
This sounds like a design phase is part of the process of getting a story done. If something is a procedural step, the best place to do it is in the workflow.
In a very simple case, I would start by having a workflow that goes
To-do -> needs design -> in design -> needs development -> <rest of process>
To-do -> needs development -> <rest of process>
This would give you two routes through your processes, one for things that need the design work before giving it to the developers, and one that does not.
There's no need for any labels if your workflow matches the process, and you'll be able to accurately report at all times. You could also create sub-tasks to hold the design part of the work, but that's a bit clunky for your users, and harder to report on.