Atlassian Team members are employees working across the company in a wide variety of roles.
November 26, 2023 edited
@Hayden Davey , thanks for the feedback! Are you referring to the reports section? Unfortunately, we don't have plans to add subtasks into agile reports. But let me know your use case and why you use this we can spin up a feature request ticket in jira.atlassian.com on it.
However subtasks are not included in the estimations per person. So How do we find out the work load of the developer in the sprint planning? As far as I see only the main issues are included.
I wish to see the total workload.
Hey @ilhan Kuzgun , hope you're well! We're looking into this one. We recognise that some users want to see the workload with subtasks and some users want to see the workload without subtasks. I'll let you know when we're done but would also love to hear your use case for it. How do you use subtasks?
We are having grooming meetings with our lead developers and PMs. In this meeting, we are focusing only on stories and their workload.
Tech leads discuss internally with their teams, create sub-tasks for each story, and decide the possible assignees and average estimations for each sub-tasks.
Before the planning meeting, we already have sub-tasks with assignees and their estimations.
In the planning meeting with all team members, we decide which story will be included in the sprint, and which won't be by checking the total workload of each person. In some cases, we re-consider the assignees of the sub-tasks if the developer has more workload than he can. Or the other developer may want to swap the sub-tasks with each other.
As a result of the planning meeting, we are dropping some stories if we don't have enough room.
Conclusion;
We need to have the total workload of each developer in the next sprint, which we are able to see in the backlog view.
@April Chi Correct! Since we can do more accurate planning of the sub-task assignee, it would be helpful for this to populate the reports as well.
@ilhan Kuzgun described a very similar process to how our teams workflow currently operates. It is essential to be able to determine the workload of each individual (based on assigned subtasks) to accurately plan what is possible within a sprint.
It is extremely helpful that we can now see sub-tasks in the backlog, though the "Workload by assignee" for each sprint is now counter intuitive given that it doesn't sum sub-tasks.
@April Chi Is there a way we can disable viewing the subtasks in the backlog view? For our instance of JIRA cloud some of the users are seeing this feature and some are still not We would like a way to not be able to see subtasks in the Backlog view and also have an option to disable the 'Subtasks' section in the 'View Settings". Please help
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Followed your suggestion but it does not work. I still see Subtasks when I filter for individual users. Funny enough I only see it when I filter for individual users, when no user icon is selected Subtasks do not appear.
I want the subtasks to never appear even when I select an individual user!
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thank you for detailing this interesting behaviour. Unfortunately, I am unable to replicate it on my end.
Could you please clarify how you are filtering for the users? Are you using a company managed scrum board backlog, where are you doing this filtering? This information might help in understanding why subtasks are appearing in your specific case.
I have also tried quick filters besides the built in user picker next to the search at the top. But again, to no avail, it works correctly on my end. Could you provide a screenshot?
Ok yes, this is a company managed board, although I do have some administrative rights. I'm in a "Software Project" and we are using a sprint planning board and not a simple kanban.
In the image below I've circled where I perform my filtering, in this case my own icon is selected. I'm in the Backlog board and I've marked where subtasks are showing. I believe this is caused when I'm assisting with another "standard issue" and have a subtask under that ticket, but that ticket is actually assigned to another user.
These are the subtasks that I do not want or need to see when we are performing out planning. I'm just not sure what is causing this. Likely it's partially with our working processes, but if there is a way to remove these without having to change how we work that would be wonderful.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
From your description and the attached screenshot, it appears that the filter might not be set up or saved correctly. It is surprising that the sub-tasks appear when an assignee is not checked. To better assist you, could you please share how you have set up the filter query?
In the attached example you can see that the filter I have set up omits the sub-tasks.
I want to assure you that adjusting your workflow shouldn't be necessary. Perhaps consulting with someone from Atlassian could lead to disabling this feature for your site. However, I believe the solution I previously shared should suffice. It is important to note that this approach will also omit sub-tasks from the active sprints. If this creates any issues, you might consider setting up a quick filter specifically to omit sub-tasks, as this can be easily toggled on and off.
An easier way would be to set up a quick filter which allows display of only parent issue types allowable for the project. Once the above is created select this in the Backlog This helped me eliminate the subtasks from the Backlog view and see only the parent issues.
N.B: The sprints/iterations still will show a count of issues including the subtasks but it would also give a count of the parent issues
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April Chi I would +1 the idea that this is something that should be a toggle somewhere in board configuration.
I have teams who love sub-tasks and use them all the time; they will love this.
I also have teams who detest the UX of subtasks and, even when they create them to help them manage a particularly complex story, do NOT want to see them on their Agile boards (either 'Active Sprint' or 'Backlog').
Excluding them from the board filter may have other implications (will need to see) but that could be an option; quick filters are another one, but it feels weird to need to set a quick filter that would be active all of the time and in all situations.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rather than the "collapse" option you show, where is the option to disable the display of sub-tasks in the backlog completely, for a project or an entire Jira site?
@April Chi Similar to Patrik, I'm on a company managed project, using scrum board, but unable to see the sub-tasks. The board is in enhanced mode, as I can do the inline editing etc.
It's an interesting coincidence, as we've just had chats about disabling sub-tasks because they are not viewable in the backlog view and it's difficult to see the rolled up estimates!
Hi @April Chi 👋, I just saw this enhancement in the newsletter this morning - great! I note this was rolling out from 16th Oct although our instance hasn't yet been activated. Our new backlog enhancements are already turned on (Company Managed / Scrum) and I don't see this feature on any of our projects. Am I missing something? Do we need to activate something else? Thanks Jules :)
Atlassian Team members are employees working across the company in a wide variety of roles.
December 5, 2023 edited
It is extremely helpful that we can now see sub-tasks in the backlog, though the "Workload by assignee" for each sprint is now counter intuitive given that it doesn't sum sub-tasks.
Hey @Hayden Davey , thanks for the response! We're rolling out the ability to sum subtasks in workload by assignee. It should be rolled out by the end of next week. Please let me know if you see it and have any feedback.
If you've accidentally turned on this feature, how do you turn it back off? Having the subtasks display in the backlog is not desired.
&
Is there a way we can disable viewing the subtasks in the backlog view? For our instance of JIRA cloud some of the users are seeing this feature and some are still not We would like a way to not be able to see subtasks in the Backlog view and also have an option to disable the 'Subtasks' section in the 'View Settings". Please help
&
Rather than the "collapse" option you show, where is the option to disable the display of sub-tasks in the backlog completely, for a project or an entire Jira site?
Hope you're both well! The current way to turn it off is as a few of you have said, you can filter out subtasks within the backlog. @Haddon Fisher has explained some great use cases that I'll pass back to my team, if you both don't mind, can you explain how you use subtasks and how having them show up in the backlog affects you and your team?
Hope you're well. Can you take a full screenshot of your backlog and send it to me at achi@atlassian.com ? I can help figure out why you can't see it yet from there :)
71 comments