is it planned in the future to remove the restriction that subtasks must always be in the same sprint as their main task?
We are working with several departments on a task and would like to reflect this via the subtasks in the future. However, the assigned persons will not always work on their subtask in the same sprint.
Thanks for your informations on the new subtask backlog feature.
I agree with @Daniel Sorg , being able to set subtasks to different sprints would make them useful to us, along with being able to see the rolled up estimates and also their estimates showing up in the "workload by assignee" info:
Great to hear this announcement. Thanks a lot for your information @April Chi . It is very helpful to us to manage the workload of the team members. However, I could not reach this feature on my Jira project (company-managed project). What should I do to enable this feature? Thanks a lot.
New Addition effected the Backlog board as it includes the subtasks count when crosses 5K. Better Backlog board should has the sub tasks enable or disable like filter so that it will avoid the board to show the results.
Is it planned in the future to remove the restriction that subtasks must always be in the same sprint as their main task?
We are working with several departments on a task and would like to reflect this via the subtasks in the future. However, the assigned persons will not always work on their subtask in the same sprint.
Unfortunately, there aren't any plans to address this yet. The reason for this is it's following scrum methodology where subtasks make up parent issues, hence should be in the same sprint.
The current workaround would be to break your parent issues down into smaller pieces to reflect subtasks.
However, I've heard this feedback a lot and would be happy to chat about if you're interested in explaining more: https://calendly.com/april-atlassian/jsw. If you prefer email, reach out to me at achi@atlassian.com.
Just noting that I've responded to your email, let me know if you have any other questions / concerns.
Just to add to the email and this message, we don't have any plans to add subtasks to timeline yet, but here's the feature ticket if you'd like to vote for this feature: https://jira.atlassian.com/browse/JSWCLOUD-18677.
@April Chi I can confirm. I dont see the toogle switch, but it is stating that we use now the enhanced version + I do see the sub taks items on the backlog. Thank you!
Thank you so much for these changes! Very excited. As of right now, it seems we still do not have subtask visibility in our backlog (of a company-managed scrum project). I also don't see the Enhance my board and backlog option. Any suggestions on steps forward?
How do we turn this feature off? It's totally misleading as a Product Manager, the sub-tasks define 'How' the team will deliver the work, this is visible in Sprint Backlog (Active Sprints) section of the project.
Showing the sub-tasks is fine, but including it as the count with the number of backlog items is super mis-leading and confusing.
As a Product Manager, I want to know how many PBIs/ User Stories are in the backlog, not the number of sub-taks (how) that underpins them.
Please let us all know how we can disable the sub-task count in the Product Backlog.
Hello! This is an exciting update. We have a company-managed project, but I don't see this option in our backlog yet. Does this also apply to be able to view child issues in the backlog? Thank you!
71 comments