Jira issues types

For well structuring features development with Jira issue types, we define the following structure

Default issue types

Epic

It is the highest organization level. It can include other tasks. It is useful when a feature needs the implication of different departments.

Task

It is the most common issue type used for the definition of what needs to be done. It must be as specific as possible. If the task is too complex, it must be divided in subtasks.

Subtask

In those cases where a task has too many definitions, it is a good practice to divide it in subtasks to be more atomic.

Custom issue types

It is recommended to have these custom issue types to keep a better track of the requirements, defining their own issue fields.

• Design
• Copy
• Backend
• Frontend
• QA
• Data

For creating a new issue type, go to project settings and add a new Work type of type Story. Use these names and different icons for each of them.

Custom fields

Issues types can have a variety of different fields presented on both their preview in the board and in their detail page.

To create a custom view for each issue type, go to Jira settings - Screens. In Screens Scheme, you will be able to customize the screen fields per each issue type.

After that, you can assign the Screens for each issue type.

Fields per issue type

• Epic
  • reporter
  • priority
  • sprint
  • story points
  • documentation (custom field of type URL)
• design
  • assignee
  • sprint
  • story points
  • priority
  • team
  • Acceptance criteria (custom field of type Checkboxes)
• Backend, Frontend and QA
  • asignee
  • sprint
  • story points
  • priority
  • team
  • development
  • Acceptance criteria (custom field of type Checkboxes)
• QA
  • Definition of done (custom field of type Checkboxes)

Example

You can see here how tasks would be organized. The icon of the issues note what issue type they are, and each of them can have their own issue fields.