Sub-task or Create issue

[A B]

Now in projects, if I have a task that needs 2 sides, for example, a sign-in page, there will be front-end and back-end tasks, so here we have 2 options:

• Create a task with the details, and create 2 child issues to the main one (Front-end and Back-end)
• Create 2 tasks, one for Front-End, and the second one Back-end, and link each one to the other (No child issues)

Would appreciate what is best and why

[Bill Sheboy · Accepted solution]

Hi @A B -- Welcome to the Atlassian Community!

When you discussed this scenario with your team, what did they think was the better approach to try?  Why did they think that approach was better?  What other approaches did they consider?

Having that conversation will help the team decide how to proceed, and give them information to monitor if things are not working as expected, allowing them to select other approaches to try.

Kind regards,
Bill

[A B]

Hi @Bill Sheboy !
Thank you for welcoming me and your suggestion!

After I discuss it with them, I will be sure what is best for the team.

Thank you,

[Varsha Joshi · Accepted solution]

My preference would be Option#1, makes it easier to track from a feature perspective.

[A B]

Thank you @Varsha Joshi ! I appreciate your response

[Summer.Hogan · Accepted solution]

Hi @A B - Welcome to the community! If you want another opinion, I also would go with Option #1 as the tracking in the long run will be more efficient. 

[A B]

Thank you for welcoming me and also for your explain!

Will try it