Actually, JIRA Agile will not count sub-tasks in. What we advise is to move them up one level. For instance, change issues to epics and sub-tasks to issues. THis way you will be able to manage them in a more feasable way.
If you'd like to take a look at a very detailed answer regarding this matter, please see here:
I agree, that link wasn't helpful at all. Also, the "change issues to epics" doesn't work when those issues already belong to epics, ie. Epic #1 has Issue #1 has Sub-Task #1. Converting Issue #1 to an Epic is impossible because then it can no longer be a member of Epic #1 (since Epics can't belong to Epics).
this for me is a major frustration with JIRA agile. I would like to associate a number of subtasks to a story and the distribute across the team (which could be in a different timezone) and then manage them across the Agile Board with all the easy to read transparency that this view gives me. Story points not being aggregated up from sub tasks is another major frustration.
I agree. I am introducing SCRM board to my organization. I am used to logging Story Point on User Story (Story Point = ROM) and estimating hours and resource mgmt, on Sub Tasks. I would expect burndown charts to be based off of remaining hours of sub tasks.
Please advise how to accomplish this using Jira.
Still a problem. So frustrating. Trying to workaround with odd/crazy board configurations and that also doesn't help - subtasks (or parent, or anything that would let me connect an issue to another issue...) aren't a choice in the issue detail view config for a board either. Atlassian you makin me crazy!
This is causing our org major issues. I can't overstate this. The other "fix" to this would be allowing "tasks" to report to "stories." Never understood the rationale of putting "tasks" and "stories" on the same level anyhow. Is there nothing that can be done to elevate this so it can be addressed?
Adding another comment saying this should be completed.
Quote from the article you linked, "All of that said one of the key precepts of Agile is finding the way that works for you." Using Sub-tasks works for various organizations, so why not develop what users need instead of forcing them into a specific workflow that may not be as effective.
This is not a solution. I absolutely need to have subtasks showing up on my scrum board. We are already using epics. We cannot escalate subtasks to tasks.
The work around I'm going to have to go with is a new sprint planning kanban board and a kanban sprint board.
Just another way jira has too many unnecessary configuration options and not the options we actually need.
I just googled this topic and found this thread - I'm having this exact issue and am very frustrated with the fact that this feature is not enabled. Is Jira even agile when it comes to developing their software? I'm very surprised this has not been tackled yet as it seems like a no-brainer.
What I am specifically looking for: in the Active Sprints view, for ALL stories to show ALL subtasks in that view. I have a weird bug or whatever is going on, that shows only 8 Stories with subtasks, and the rest of the stories are only "other issues", even though they have multiple pointed sub tasks as well.
1. I have found I think a fix for this, just don't know if it will last. So far it works as I want it to.
To see all subtasks:
- Go to the 3 dot menu at the top right of the screen where your picture is
- Click on the 3 dot menu and then tap on "Expand all swimlanes"
- If that doesn't do it:
- Tap on "Collapse all swimlanes"
- tap on "Expand all swimlanes" again
2. : October: 2 monthes later, still having the same issues. However, discovered yet another fix, try this if number 1 is failing you:
To show stories in current sprints that are missing and or have stories break out their sub tasks in swimlanes:
- When creating a story, or sub task take a look at the "Fix version"
- Assign the Fix version to the version that you are developing for
- This will enable the story or sub task to be seen in the correct area/swim lanes.
With my company, we had "Alpha" as the boards "fix version". When anything, story, bug, sub task, was not assigned as "Alpha" it would not show up in the swimlanes, and immediately throw the story in the "Other issues" section, or simply not show it at all. When assigning the Fix version, it immediately fixed the problem.
Or you could just switch to Pivotal Tracker, and never have frustrating issues like this again.
Thank you for posting your solution. Although I didn't get it to work right away I discovered that it was effective if I turned all of the filters off as well as collapsing and re-expanding the swimlanes. Just thought I would mention it on the offchance that this is the problem with your other board which is still failing.
Benito already answered this question, but that "answer" was not very helpful. Obviously if you have 10 issues with 10 sub-tasks each, you're not going to want to convert them in to 100 un-categorized tickets just to use the scrum board! Unfortunately it seems a true answer doesn't exist, so the best one can do is explain why Atlassian won't solve this problem. The link Benito provided does just that, but since he didn't provide a summary of it, allow me:
Atlassian has a very narrow idea of how their tool should be used, and when they use it they don't put story points on sub-tasks. Instead, they put hours on sub-tasks and use them for tracking. The way they see it, if they allowed sub-tasks on the scrum board it would amount to mixing planning (story points) and tracking (hours).
What the article doesn't actually say, but implies, is that they can't imagine anyone wanting to put story points on sub-tasks and use them for planning. This seems to be the real reason why there's no option to show sub-tasks on the scrum board.
My favorite part of the article was the end. After they just finished explaining why they won't allow you to use their tool in a way that works best for you they write:
"one of the key precepts of Agile is finding the way that works for you"
Thanks Atlassian, so I should find a way that works for me ... as long as it's exactly the same way you do it?
@Benito Picarelli you or the Jira product manager may find these comments useful. I love your tool, but there are certain quirks like this one that make it good instead of great. I would have expected sub-tasks to appear on a jira board, but apparently they don't... Now I have to convert all my subtasks to issues and link them... not so much fun.
The big issue here seems to be a focus on generalist developers and not specialists.
If I have an Epic (big goal) with multiple user stories (as a user I want to add some stuff to the widget) but I have a small team of specialists front-end and back-end developers this becomes a serious issue to balance. The user story has sub-tasks for the both front-end and back-end developer. However the back-end developer is behind schedule due to high priority bug fixes. In order to give my front-end developer work for the sprint I have to pull in the user-story and bury the back-end developer even further? I have to disassociate the user-story from the real epic in order to make it an epic? I have to change the sub-tasks into tasks and relate them? There's a specific connection between these types of issues, particularly from a reporting standpoint. Why force all this jumping through hoops? For small teams of specialists it seems impossible to use agile and be forced to using kanban
+1 for allowing full use of sub-tasks within agile boards, ensuring that hours & story points (specifically hours in my case) roll up and are summed correctly. Epics are better for large groups of related issues that span multiple sprints, while sub-tasks are best for sub-dividing a single task that will be completed within a single sprint.
I have found a temporary workaround:
Now each ticket in the Agile Board will also list any sub-tasks it has.
Screen Shot 2016-01-22 at 9.03.56 AM.png
Screen Shot 2016-01-22 at 9.04.34 AM.png
+1 to have an option to see sub-tasks on Agile Board.
This is not about story points only. It is often really necessary to observe:
For sure separate JQL filters may be created as a workaround, but this is a tricky part and this option does not let you to see 'the big picture': you have to jump across multiple tabs back and forth and remain unconfident you did not missed anything.
I just encountered this problem, and it appears that even the parent issue is not shown on the board, although when you go to the issue navigator, they're all there. I actually opened a support ticket with Atlassian because I thought were were either doing something wrong or it was a bug. Well, I still think it's a bug, actually! Good grief, even if it's a sub-task, it's still part of the sprint and should be shown!
just stumbled over this conversation and would like to share my thoughts. I have not read the lengthy Atlasssian statement, so bare with me if i might repeat something...
Here is how some of our teams using subtasks:
In this case subtasks are not relevant for planning, nor for statistics.
What do you think?
@Benito Picarelli, is there an update on this issue? Seems like it is affecting many, incl myself, so would hope that it is fixed, or at the top of your backlog.
I think it's standard to create sub-tasks of a Story, assign to different developers to complete their sub-task and want to see it all in the board. And this includes seeing the effort per person.
+1, please allow full functionality for sub-tasks
(my sprint planning takes user stories and breaks it down into subtasks, if after the breakout of work we realize it's too much we may push it to another sprint and split the User Story... without full visablity to the work involved working in JIRA is a nightmare)
I have come to the conclusion that Atlassian is being deliberately pedantic about the whole Epic/Story/Subtask thing, and the "Scrum Masters" of the world are desperately trying to shoehorn explanations into why this is a good idea. I think its a case where common sense is being over-ridden by pedantic definitions and rigid adherence to Scrum theory, which, ironically, is the opposite of what Scrum is meant for.
Our team has simply given up on sub-tasks, and we don't use the feature at all.
This addresses all our needs, and gives us all the flexibility we desire. It also allows us to not get caught up in whatever bull**** definition Atlassian may have for different ticket types. We use them as it makes sense to us.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs