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,461,804
Community Members
 
Community Events
176
Community Groups

What is the best way to identify whether a ticket needs design (UX/UI Team) input?

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. 

Any suggestions? 

2 answers

1 vote

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>

and

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.

hello @Amy Blower ,

You can use sub-task for this case. 

If a task need work from multiple teams (dev/design), you can create a sub-task for each team. 

when all the sub-task are done, you main task can automaticaly be closed.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events