Hierarchy of Jira's issue

Artur Mkrtychian_x867x0

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?

 

For example,

Registration feature
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

 

 

 

Nic Brough -Adaptavist-

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)

Story:  Registration

• Task: Main site - Design signup button
  Task: Main site - Adding signup button on the main site
• Task: Signup - Design signup form
• Task: Signup - Layout of the signup form
• Task: when done - Connect signup form to the API
• Task: when done - Make API for the registration

Which is a little clunky. 

If you have Jira Software, I would be tempted to do this:

Epic:  Registration

• Story: Main site
  • Task: Design signup button
  • Task: Adding signup button on the main site
• Story: Signup
  • Task: Design signup form
  • Task: Layout of the signup form
• Story: when done
  • Task: Connect signup form to the API
  • Task: Make API for the registration

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.