When creating an issue, further details can be added on the issue registration page. Properties like description, issue type, assignee, priority, start, and due date are the basic fields that you can input for more details.
In Backlog, you can find 2 main sections of input fields on the issue registration page - description field and condition fields.
Description field
The issue description is a rich text field that lets you describe or summarize the issue details. It's important to write descriptions so that other users can understand and follow the content and workflow. For example, if an issue concerns bugs in developing software, writing in the description about how the bugs occurred will help the developer team understand the scenario and resolve it quickly. Similarly, if this is a customer support issue, the support staff will use the description to explain the customers’ questions.
You can use functions such as the @mention function to notify a user or team about the issue or apply text formatting such as bold, checklist, or table in the description field.
To learn more about the issue’s description field functions and editor details, refer to the Issue and comment editor support article.
Condition fields
The condition fields help you to categorize issues so that they can be organized and retrieved easily. These fields include issues types, assignee, category, start, and due date, etc.
- Issue type
You can change the issue type based on the issue or task you created. Issue types can be customized by all members on the project settings page. - Status
By default, the issue will be assigned as Open status for the first registration and it cannot be amended. Users can update the issue status later after the issue has been registered.
The administrator or project administrator can further customize the issue status on the project settings.
Did you know?
Custom status feature only available to the Starter plan and above. - Assignee
You can assign the issue to a member or to yourself.
Did you know?
Only one assignee can be assigned for each task.
- Priority
By default, Backlog provides three priority - “Low,” “Normal,” and “High.”
- Milestone
Milestone act as a plan and you can link an issue to a milestone or multiple milestones. New milestones can be added by all the members on the project settings page or on the issue registration page by clicking the + button beside the milestone field.
Milestone will be associate with the Burndown chart. To learn more about how the milestone and Burndown chart works, refer to the Burndown chart overview support article.
- Category
Category helps you classified issues into groups and you can use them as a filter when filtering issues. Multiple categories can be added for each project by all members on the project settings page or by clicking the + button beside the category field on the issue registration page.
- Version
Version can be used to specify the version (released milestone) that the issue is related. Multiple version can be added for each project by all members on the project settings page or by clicking the + button beside the version field on the issue registration page. - Start Date and Due Date
You can set a timeline for an issue by update the start and due date.
Did you know?
- Start date only available when the administrator or project administrator enables charts function in the project settings.
- Chart function only available to the Standard plan and above.
- Estimated Hours and Actual Hours
Estimated hours allows you to set the planned hours required to complete the issue. While actual hours can be set while updating the issue to record the time spent on the task. Estimated hours are required to have accurate tracking of milestones progress via the Burndown chart.
Did you know?
- Estimated and actual hours function only available when the administrator or project administrator enables charts function in the project settings.
- Chart function only available to the Standard plan and above.
- Custom Field
Besides the general fields from Backlog, the administrator or project administrator can create a custom field to support the team’s needs and it can be used to filter issues within the project. The custom fields will appear as condition fields that let the members input more details about the issue.
To learn more about how to create a custom field in a project, refer to the Create custom field support article.
Did you know?
Custom field feature only available to Premium plan and Enterprise plan.