Right now there is no ability to add Task to the Story. What issue type do use for requirements? How do you organize hierarchy of Jira's issue?
Allow guest to register on the web-site
as an unregistered user
WHEN I go to the main site
THEN I should see a link to signup as a user
- Design signup button
- Adding signup button on the main site
an unregistered user
WHEN I go click on 'signup'
THEN I should see a form allowing me to sign up to the site
- Design signup form
- Layout of the signup form
as an unregistered user
WHEN I fill out the signup form
AND click submit
THEN I should receive a confirmation email with a link that activates the account
- Connect signup form to the API
- Make API for the registration
- Connect e-mail lib to the back-end
- Logic of generating activation link for new users
- Sending activation link for new users
With plain Jira, you're a little stuck if you want to split up the story like that. Best you can do is use sub-tasks with indicative summaries: (Note, I've said "Task" here - that assumes you have an issue type called "Task", it is a sub-task-type, and you add it to your project issue-type scheme)
Which is a little clunky.
If you have Jira Software, I would be tempted to do this:
I'd also be tempted not to call that issue type "story" as they're not really big enough.
The issue types are entirely flexible, so you can name anything however you want.
Thank you for the reply!
You can include Story and Task in the Epic.
But in Jira you can not include Task in the Story to make the following:
Yes, because they're usually just useless noise in a backlog. You select stories to work on in a backlog, and the sub-tasks are a wholly owned part of that.
You wouldn't try to build a car for someone and deliver it without any wheels because you've decided to do those later.
Nic's suggestion to use sub-tasks (with a "Task" of the sub-task issue type) is indeed the best way to do this without a third-party app.
However, if you are looking for more flexibility when it comes to organizing issues, you may want to look into some third-party add-ons. Structure for Jira, in particular, provides an easy way to build hierarchies of issues that can be adjusted to your specific process. You can have as many levels as you want (which is useful when you need to break down larger tasks) and it allows you to visualize your work and track your progress. I’d be happy to share more information with you, should you decide to give it a try.
Please feel free to write to firstname.lastname@example.org or to me directly for further details.
I look forward to chatting with you.
ALM Works, Inc
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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