What is the way we can add/link a Task to a story.
I was able to add story and task to an EPIC but not able to add task to a story.
The JIRA Agile add on does not support that concept. If you want, use Issue Links to link the issues together.
We also need this feature:
Epic -> Story -> Task -> Sub Task
I'm wondering that it isn't possible with Jira
Hello Everyone,
Several teams have interacted In this thread for the past few years, so here is an updated answer for everyone interested in this matter:
Today, Jira Cloud standard and free plans allow the following hierarchy to be made:
Epic > Standard issues (Story,task,bug) > Sub-task
On these two plans, this hierarchy can not be customized or changed, however, we have some improvement requests to consider this option in the future:
As a Jira Software user, I want to have support to Initiatives and other levels by default
Sub-issues should be able to contain their own sub-issues
Improve Jira issue type hierarchy
For now, we have the following options to achieve something similar to the requests above:
1 - Upgrading Jira to the Premium plan, you can use advanced roadmaps to properly create new hierarchy levels as described in the documentation below:
Configuring hierarchy levels
2 - You can also use the issue linking functionality. This feature does not work in a hierarchical way but can give you an alternative option to relate one issue to another in Standard and Free plans.
Additionally, Feel free to vote and watch the improvement requests linked above to increase its priority and also receive notifications about any updates.
Thanks!
what is the hierarchy (parent-child) we can use in JIRA
There is no heirarchy in JIRA other than parrent issue and sub task in JIRA. If you want structure, you migth want to consider Strucurte Add on (https://marketplace.atlassian.com/plugins/com.almworks.jira.structure).
You can link a task to an story by using JIRA regular links and track those relationships from JIRA itself or by using an advanced links viewer like Links Hierarchy.
"parent" and "child" are only names. You could create such custom link type on JIRA in order to represent a parent-child relationship between Stories and Tasks...
An story is parent of a task and a task is child of an Story.
However, the parent-child relationship is also used by JIRA for sub-tasks:
An issue is parent of a sub-task and a sub-task is child of an issue.
So, to avoid confusion, you could create a new link type: "owns-belongs to" (for instance) to represent the same relationship:
An Story owns tasks and tasks belonging to stories.
O whatever else link type you need.
One advantage of regular links regarding Agile is that they bring a rich expressiveness. For example: Before to start an sprint (Sp1) you could discover that a task (A) depends from other task (B) which does not belong to the same sprint. In this case, you might want to create a link "depends" between the task A ans the task B.
In this simple case, when you are going to plan the task A you need to be able to see that it depends on the task B in order to include the task B in the same sprint or delay the task A until B is resolved. This is a simple and common case where the simply parent-child relationship is not enough.
Many, many companies are using a lot of different issue types (like bugs, test cases, etc) and a lot of link types (the bug X affects to the task Y) to work with Agile beyond Epics, Stories, Task, Subtasks and parent-child which are an small set of elements you can use on Agile, but really there is an endless lot of possibilities to bring Agile benfits to JIRA and JIRA benefits to Agile. And regular links are one of such benefits that you can take advantage from Agile as it is built on top of JIRA.
Is there any way to create a task and add it to an existing story?
This is pretty much useless. It gives no visual hint, just a bunch of reference, it is like comparing a command line browser to a graphical browser. In both ways, the expected information and data is there, the only difference is the representation. Which one is better?
hehe, so don't use MS Windows nor Linux nor Mac and turn back to MS-DOS!!
I meant that the GUI is better so would be in JIRA (as reviewing Storys with its linked tasks is useless in its current form)
I continue to be amazed at how many logical and sensible questions I see posted here (because I have had the same myself), only to be told "Well, that's not how JIRA handles fill-in-the-blank." But I guess Atlassian knows what we want more than we do.
I think this has your exact answer, official from Atlassian: https://confluence.atlassian.com/agile065/jira-agile-user-s-guide/working-with-issues/creating-an-issue/creating-a-sub-task
In short: no.
This is not an "answer" just a how-to on creating a Sub-Task. This article has no information on what a Sub-Task is, what its role is in a project, etc. And Sub-Tasks are not visible in Scrum board.
Did you read the original question and comments about the "problem" here?
If you follow the directions there, it achieves the goal of the Answer.
Maybe you should try it instead of throwing a fit.
Other ways to find the sub-task control are the ellipsis (...) dropdown menu on the Story, or type '.' key command while viewing the story and then start typing "sub".
Actually we need this feature too. We divide Epics for several small Epics, because there is no easy way to link new issue/dev-task to Story during creation.
Doesn anyone find solution, to add such custom field on issue creation page?
P.S. Use link button with selecting dependence to Story, it's not easy way.
I was expecting this to work this way as well and am dissapointed tasks are just free floating entities. Heirarchy is hard to acheive with Jira and there doesn't seem to be a good way to use it to link everything together.
You can't technically add a Task to a Story.
However, what you can do is convert a Task to a Sub-Task and attach that to a Story (or anything else for that matter). Doing this will now make those tasks appear in the Story's details with a progress bar indicating the progress.
I hope this solves what you're looking to achieve. I'm unsure how this affects the data tracking though.
We are trying to group cards on our Kanban board based on Epic Links, but subtasks cannot have an Epic Link, which then renders the use of subtasks almost worthless. It helps tracking subtasks for a given Story, but that still doesn't allow us to group everything based on an Epic.
If subtasks could have an Epic Link, then this probably wouldn't be a big deal.
I think the idea is that sub-tasks can't be associated with an Epic because they should only be part of its parent.
An Epic shouldn't care about the details of a story. Only the high-level Story, Task, Bug, or whatever type that can have sub-tasks.
Sadly, by default, JIRA doesn't accumulate the story points mentioned in sub-tasks to its parent. You'll have to maintain the total amount in the parent type manually.
I am wondering the same thing, is this possible?
Wish I could vote this up many timess. We really need Epic -> Story -> Task -> Sub Task with each element having a unique identifier (#). The linking of tasks to a story is cumbersome.
Agreed. Still need this which I'm seeing as at least a 3 year old request. The linking process is time consuming and requires a whole lot of extra clicks that seem unnecessary.
I'm looking for the same thing!
It does now, I was having an argument with a colleague, that Jira does not have this feature, then he showed me :-) Silent feature upgrade rulez (of course, this is the Cloud version).
It looks like you're new here. Sign in or register to get started.
