Issue overview

In Backlog, a piece of work or a ticket within a project, such as a task is represented as an issue. Issues help you stay organized and keep track of tasks in the project and their timelines.

To further define your issue, you can term your issue into different issue types such as task, bug, request, improvements, etc. Issues can be assigned to the project members and members can further collaborate on the issue by updating the status, provide their comments, and notify a group of members about the issue.

Issue structure

In Backlog, the issue structure consists of 2 tier - Parent Issue and Subtask. The parent and subtask function is useful to help the user to break a bigger task down into smaller parts. 

Did you know?

Subtasking feature only available to the Starter plan and above users. Administrator or project administrator required to enable the subtasking feature in the project settings in order for the project members to create subtask.


Subtasking lets you split a parent issue into smaller child issues to helps you:

  • Smoother management of large projects or large tasks.
  • Easier tracking task delegation and progress.
  • More specific individual tasks can be assigned to multiple people in which members can work towards the tasks at the same time. 

To learn more about adding issues and subtasks, refer to the Add issues and subtasks support article.

Issue properties

While creating an issue, further details of an issue can be added on the issue registration page. In Backlog, you can find 2 main sections of the input fields - description and condition fields. Issues properties like description, issue type, assignee, priority, start, and due date are the basic field that you can input. 

To learn more about the description and condition fields, refer to the Issue properties support article

Issue key

Issue key is a unique identifier representing every piece of work in the Backlog project. When issues are registered in a project, issue keys will be generated and assigned to each registered issue. 

Issue keys are made up of the 2 main components: 

  1. The project key (eg: MKTG)
  2. A sequential number of tasks registered in the project (eg: 12 / 60)

To learn more about how to use the issue key, refer to the Usage of issue key support article. 

Did you know?

Issue keys are not amenable or customize. Only the project key can be changed by the administrator or project administrator. 
-1 people think that it is helpful. Was this helpful for you?

Have a question we didn't answer?

Contact support