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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Which is the bes

unnikrishnan m
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2023

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.

1 answer

0 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

hi @unnikrishnan m 

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

  1. Reporting needs for measuring team performance and their activities.
  2. Product complexity and number of members within each team.
  3. Your team readiness and their preferences for different setups.

I would recommend

  • Prepare two working models according to your team structure, product complexity and reporting needs.
  • conduct a discovery session with all teams to have a collective feedback and buy-in for your working model accordingly.
  • Explain to them why one model could be useful and why it could be challenging according to your needs. count also for their needs and work together to define the final model.
  • Conduct retrospective after one or two sprints to improve the working model.

This way it will leverage team-work, collaboration and ownership.

Good Luck and let me know if you have further questions.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events