Field mapping
Last updated
Last updated
After a Hurdle workspace has been connected to a Jira site and project, you'll be prompted to map estimate, issue type, issue status and priority fields.
Estimates can either be mapped to Jira's time-based estimate field, or to a custom field. When mapping to a custom field, story points or time can be selected as the estimation unit.
During the integration setup, issue types in the connected Jira project will be auto-detected and mapped to corresponding issue types in Hurdle. You can edit how issue types appear (name and icon) in Hurdle.
Like issue types, issue statuses in the connected Jira project will be auto-detected and mapped to a corresponding issue status in Hurdle. Each issue status needs to be associated with a status category in Hurdle:
New: Indicates that an issue has been created but has not yet been reviewed or scoped.
Ready: Indicates that an issue has been reviewed and scoped and is ready for work.
In progress: Indicates that an issue is open and is currently being worked on.
Closed: Indicates that an issue is closed and work was completed.
Null: Indicates that an issue is closed and did not need work (null issues will not count towards total counts).
Issue priority values in the connected Jira projected can be mapped to an issue priority field in Hurdle. Mapping the priority field is optional.
Once estimate, issue type, issue status and priority fields have been mapped, a confirmation screen will detail the settings and provide a summary of how many issues will be synced when the integration is initially enabled.
After the integration has been enabled, all updates to issues in Hurdle will sync to Jira, and vice versa.
• Jira epics will map to
• Jira standard issues will map to (these are the issues that will appear in the backlog and sprint planner)
• Jira subtasks will map to (these issues will be nested under task issues)
