Issue type standard in agile

Question

Hi,

Can somebody please confirm if there is any standard which says:

1. User story will be created under Epic

2. Task will always be created under User Story

3. Sub-Task will always be created under User Story

4. Bug will always be created under User Story

5. Task cannot be created under Epic

6. Sub-Task will always be created under User Story instead we can create it under a Task

If there is some restriction to be given then how to archive in jira?

Regards

Jack Brickey · Answer

it is worth noting that Jira does employee three different hierarchical classes of issuetypes and with these classes there is underlying behaviors associate w/ each class; displayed here in the hierarchical relationship * Epics* Issues: Story, Task, * Sub-tasks - can also include

Andrew Laden · Answer

Natively, there is not any restriction in jira that would enforce that sort of model. Jira is very flexible, to allow you to configure it how you want.

Stories, Epics, Tasks, Bugs etc are all just names of issue types, how you use them is up to you. There isn't necessarily a "parent/child" or "under" relationship.

You can do things with required fields and with conditions/validators to enforce certain items, but that is your choice. for example:

* you could make the "Epic link" field required on Story issue types.
* You could not have the epic link field on tasks.
* You can require Task to have links to stories
* You can prevent subtasks from being created under stories.

The only "hard" rule is that a subtask (or any subtask issue type) can only be created under another ticket.

"The great thing about standards is that there are so many to choose from"

Jack Brickey · Answer

* That certainly is “standard” in my book
* this cant be done in Jira. Task is at the same level as Story.
* Not always. I only do so when my story is not obvious and needs to be broken onto smaller work items.
* I never create a bug under a story. I may link a bug to a story to convey a bug was found while testing a story.
* i often create tasks under epic
* i often crest sub-tasks under both