Issue Specification


The whole team should be involved in this stage of the sprint planning.

Decomposing Into the Subtasks

You can divide a large issue into smaller and specific actions. This will allow you to make work progress more manageable and transparent. You will know exactly which subtasks have already been completed and you will be able to estimate the amount of work remaining.

The list of subtasks is displayed on the detailed page of the parent issue and on the board.

List of subtasks on the parent issue page


Subtasks on the board in the form of additional tracks

For each subtask, you can specify its own executor, rating, priority. You can also establish links with other issues, add comments, files.

How to Add Subtasks

  1. Open the parent issue for which you want to add a subtask.
  2. Click New Subtask (1) or enter a name in the line to create it quickly (2) and press Enter.
  3. If necessary, change the order of subtasks in the list using the Drag&Drop method (3) in the parent issue or on the board.

Readiness Criteria

Make a checklist of readiness criteria. It will help the executor to structure his work, not to forget about important things and clearly understand what result should be delivered at the completion of this issue. You can describe each item as precisely as possible. Character limit is 65,000.

The checklist has a progress bar, which clearly shows how many items have already been completed and helps you to determine the percentage of the issue readiness.

To change the order of the checklist items, use simple drag and drop.

Evaluation of Labor Costs

When planning a sprint, it is important to determine the total amount of work, the team will be able to complete in a given time frame and evaluate each issue.

Use a convenient unit of measurement – 4 hours (half working day), day, an hour or abstract points.

For example, if you evaluate one issue at one point, and the second at five points, this will actually mean that it is five times more difficult to implement the second issue than the first one. However, it will not necessarily mean that the second issue will take five times longer than the first one.

Please note: Issue that have got too high rating, for example, 3 days, should be decomposed. The duration of one subtask should not exceed one day. Otherwise, you will not be able to see the progress of the work, and the executor will lose the pace of work. If the team cannot evaluate any story due to lack of information, this issue should be excluded from the sprint and the team will need to conduct additional research

Adding the ranking of labour costs

Go to the detailed page of the sprint to see the total assessment of the issues and, depending on it, add new issues or remove unnecessary ones.

Going to the detailed page


Detailed sprint page

Assigning the Responsible

Assign the responsible on the issue page or using drag and drop. For ease of dragging, roll up the list of categories and other columns if you have a lot of them.

Assign the responsible person to several issues at once by selecting and dragging backlog elements to the appropriate folder.

Determining the Order of Execution

In the sprint backlog list or on the board, you can change the order of issues display using the Drag & Drop method, if you want the team to execute them in a certain order.

Note that the board always displays issues with subtasks first.