Jira status mapping
Status mapping allows for two-way sync of Jira issues and Hyperproof tasks. For issues and tasks to sync, statuses must be correctly mapped. Note that proof uploaded in Jira can be uploaded to Hyperproof, but not vice versa.
Statuses—such as To Do, In Progress, Waiting for Feedback, and Closed—are found in every Jira ticket. Throughout a Jira issue’s life cycle, statuses are changed and updated depending on what stage the issue is in, e.g. Bug Testing.
Because Jira is customizable, and it’s likely that your organization has a modified workflow with unique statuses, Hyperproof needs to know how to associate your Jira statuses with its own task statuses.
When configuring Jira, it’s important that the statuses in both platforms match. For example, if your Jira issue status is To Do, it should be mapped to the Hyperproof task status Not Started.
Tip
More than one Jira status can be mapped to a Hyperproof status.
For example, you might map the Jira statuses Open, Blocked, and Reopen to the Hyperproof task status In Progress. The Open status is the default because it is listed first. If you want Blocked as the default, for example, simply drag-and-drop Blocked before Open.