Issues and subtasks

Issues are the building blocks of your Hurdle workspace. They can represent new features, improvements, bugs – or any other piece of work.

If you're integrating with Jira, your issue settings from Jira will be mapped to Hurdle. Any new issues created or updated in Jira will appear or update in Hurdle, and vice versa.

Creating issues

Issues can be created from any screen within your workspace, by clicking Create issue in the sidebar. When clicked, a modal will appear where issue details can be entered.

Issues are automatically assigned a unique issue prefix and are required to have a name, type and status. Other fields that can be set when initially creating an issue include assignee, estimate, target date, and labels. Issues can also be added to a project.

Updating issues

Issues can be updated by clicking on the issue title in a table, list or on an issue card. Regardless of who the original creator of an issue is, all workspace members will be able to edit the title, description or field values of any issue.

Issue fields

Issue fields add context to and provide information about specific issues. They appear on issue cards and in lists and tables. There are fields that are required and always visible, optional and always visible, and fields that can be enabled or hidden.

Field	Set by	Required	Notes
Issue prefix	Hurdle	Yes
Issue type	User	Yes
Issue name	User	Yes
Description	User	No
Created by	Hurdle	Yes
Created on	Hurdle	Yes
Assigned to	User	No
Estimate	User	No
Updated on	Hurdle	Yes
Target date	User	No
Project	User	No
Parent	User	No	Only subtasks can have parent issues.
Workstream	User	No
Sprint	User	No
Priority	User	No
Severity	User	No

Creating subtasks

Subtasks can be created on an issue when a set of work is too large to be its own issue but too small to be a project. Subtasks are related to their parent issue but will not share the parent issue's properties. Each subtask can have its own assignee, status, estimate, target date and labels.

Individual subtasks will not appear in the triage queue, backlog, workstreams or sprint planner. Only their parent issue will appear.

If a parent issue has subtasks, an estimate will need to be set on each individual subtask. The roll-up of the estimates of each subtask will be the estimate for the parent issue.

To create a subtask, open the desired parent issue, select the Subtasks tab on the issue card, and click Quick add subtasks.

Convert subtasks into issues

After a subtask has been created, you may determine that it should actually be its own issue. To convert a subtask into an issue, click into the subtask from the parent issue card, and change its issue type.

When a subtask is converted into an issue, it will be disassociated from its parent.

Deleting issues and subtasks

To delete an issue or subtask, click into the issue or subtask card, click additional options at the top right of the card, and select Delete issue.

Deleting issues is permanent. A deleted issue cannot be recovered.