Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Add task to story


How can I add a task to a story?

Here Földes László says it works now. See answer from February ‘18

i want to close the story ater the related tasks are done.

best regards

4 answers

1 accepted

1 vote
Answer accepted
Dave Norton Atlassian Team Mar 27, 2018

HI Marcos,

Adding a subtask should be as simple as:

  1. Viewing your issue
  2. Clicking the "More" menu
  3. And then choosing "Add Sub-task".

Let me know if this isn't working for you or if I've misunderstood :)

As for the second part of your question (closing a story after the related tasks are done); that's a little more complex.

You'll probably want to make use of Jira Misc Workflow Extensions; specifically the "transition parent issue" post fuction.

The idea is that you'll use a post function to transition the parent issue (on the close or completion of a sub task), with a "Linked Issues Status Validator" that checks if all the linked issues (i.e, sub tasks) are closed. 

So, to put this all together:

  1. You have a workflow for your sub tasks
  2. When you close a sub task, the post function will transition the parent issue to the closed state.
  3. You'll need a validator on this transition, which checks to see if the parent issue's linked issues (sub tasks) are all closed - if they're all closed, the validator returns true.

Let me know how you go!


This doesn't answer the question. As the OP says, Földes *specifically states* that you can add tasks, as of February 2018.

We cannot comment in that thread (moderators locked it), but please can you explain how to create Tasks in Stories -- or can you confirm that Földes was making an incorrect statement, and this feature has NOT been added?

Like # people like this


How can this obviously needed feature is not obviously available or cannot be found. Your UI sucks!! 

Here's how to implement: Go to task: allow to add a task from link option on a story. Or, go to a story,  allow add a task from link option. If that's hard, allow it from ... button/meatballs menu.

True that

Like # people like this

Hi Marcos,

I put together an extension called Agile Docs which lets you do exactly this.

It allows you to create your epics, stories and tasks in a nested google doc and automatically creates relationships between them.

If you want to create a Task which automatically has a relationship with a parent Story, you create a dotpoint under the Story you want to link to like below:


In the above example, the task 'this is a task' belongs to the Story 'This is another story'.

You can check out the demo here.

Let me know what you think :)

Cheers, Rhys.

Hi Rhys,

I'm quite new to JIRA, so please bare with me.

The extension you developed looks great. I'm also trying to create a task as a child of a story, but show that relationship in 'Plan' which is part of portfolio - otherwise we have a long list of tasks that are merely 'linked issues' of story's, but without any visual representation. Would this extension carry through the code that will allow me to view that custom relationship in 'Plan', or is this a completely separate nested table?

Look forward to your response,.

Hi @Ben Thomson 

Thanks for the kind words. Unfortunately Agile Docs no longer supports creating Tasks under Stories. Most people were using sub-tasks under their stories so that was the direction we decided to go. There are other add-ons I could recommend for this but I'm not sure if they'd carry through to the 'Plan' view in Portfolio. Sorry I couldn't be more helpful!

Best Regards,


Hey Ryths,


i just want to double-check with you, I'm working in a project that have 4 EPICs.


how i should put them in order with multiple User Stories of each EPIC?


and how if there are tasks and subtasks?


thanks for your support we all do appreciate that 


I'm not sure I understand the question. What is the goal of putting them in order?

Update: Hierarchy for Jira (formerly Agile Docs) now supports the ability to add Tasks under Stories. Been a long time coming but it's finally here.


Like Tim likes this

"Add Sub-task" in stories is not visible in any menu, button or whatever... so I don't understand what is the difference between a story and a simple task if I cannot add sub tasks to the story, so I end up creating a Epic that has tasks... what a disaster of UX, I only use Jira because companies are still too lazy to investigate alternatives.

Suggest an answer

Log in or Sign up to answer