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,459,289
Community Members
 
Community Events
176
Community Groups

Group Task, sub-tasks and bugs to a Story instead Tasks and bugs in Other Issues

Hi Team,

 

I was searching for the answer on the Grouping Stories with its Task and bugs along with Sub-tasks in the Board, Which I see most answers are only related to Sub-Tasks. why this kind of option isn't provided in Jira, 

 

Can anyone help me understanding the Jira board management practice for Tasks and Sub-tasks

1 answer

0 votes

Jira Software has a hierarchy of Epic -> Issue (story) -> Sub-task.  Those are the only "grouping" it does in the way you describe.

Appreciate your response, I agree to your explanation on Jira Hierarchy, but as Sub-tasks are also a issues, having Story as A issue for Epic and Tasks with its sub-tasks is not in a good view but when the issue are linked have a group on hierarchy should be a better view, instead they fall under "Other Issues", 
SPTick-1.PNG

I like to see the board, with out sub-task and only tasks and bugs under Story group, 

 

Is there a way to change the view, Appreciate your help

But that's the point - you can't "group by" something that isn't there.

On your board, your tasks and bugs are not under the stories, so it can't show that.

Bugs are actually linked as related to story not as Sub-task so this grouping as Story doesn't help and view is not as expected, doesn't show as child and parent link for Issue types, only sub-tasks.

 

So the practice should be Every task should be as a Sub-task of Story, and bugs can be as individual task,  

To do that, rename the issue type "task" to something else so you can reuse the name and create a new issue type called "task" as a sub-task type.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events