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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Which is the best method of creating tasks and subtasks in the case of following case.
We want to create a login page. UI UX, Front end, back end and QA teams are involved. Which is the best option
a) To create separate tasks to each teams.
b) To create a single task and under it create sub tasks and assign it each teams.
Welcome to the community.
One approach according to your initial proposal is to create tasks or stories for FE and BE features and then sub-tasks for QA activities.
Another approach is to create tasks or stories for FE and BE features and incorporate QA activities within the workflow.
For sure there are best practices but deciding the best model might need to anticipate
I would recommend
This way it will leverage team-work, collaboration and ownership.
Good Luck and let me know if you have further questions.
Cheers,
Karim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.