Jira fields added to Helix Plan columns by the integration are appended with (Jira) to distinguish them from other columns. Helix Plan columns added to Jira are appended with [Helix Plan]. Project-specific Helix Plan columns added to Jira also include the project name. For example, Database ID [Helix Plan, Support Project].
The Jira URL, Project - Issue Type, and Resolution fields are always synced between Helix Plan and Jira. To sync additional fields from Jira to Helix Plan, make changes in the Jira field synchronization category in the Project Integration Settings dialog box.
The following information explains how Helix Plan and Jira fields are mapped when using the integration.
Numeric columns/fields
All numeric Helix Plan columns will generate two additional fields in Jira: Summary and Stat. For example: Estimated Ideal Days [Helix Plan Stat]. Do not update or delete these fields.
URL columns/fields
URL columns/fields are available in both Jira and Helix Plan to make it easy to go to items in each application.
- In Helix Plan, the column is Jira URL (section name).
- In Jira, the field is Helix Plan URL [Helix Plan, Project name].
Attachment columns/fields
When the integration is enabled, an Attachments (Jira, <Helix Plan section>) column is available in Helix Plan, which contains links to attachments in Jira for a synced item. You can download all attachments for a synced item from Jira to store in Helix Plan. See Migrating attachments.
Other columns
The following default Helix Plan columns and Jira fields are mapped between the applications.
| Helix Plan column | Jira field | Notes |
|---|---|---|
| Item name | Summary |
|
| Comments | Comment |
|
| Assigned to | Assignee | Helix Plan supports multiple assignees, but Jira does not. In Jira, the Assigned to [Helix Plan] column is displayed. It contains a list of all assigned users from Helix Plan. The first user in the list is set as the Assignee in Jira. To assign an item in Jira, use the Assign to functionality. Jira updates the assigned user in the Assignee field and adds one user to the Assigned to [Helix Plan] list. If you want to assign multiple users from Jira, you must use the Assigned to [Helix Plan] field for assignments. |
| Originally created by | Reporter |
|
| User story / Detailed description | Description |
|
| Work remaining | Logged Work, Estimated, Remaining | Estimating works differently in Helix Plan and Jira. In Helix Plan, Estimated ideal days or Points are used in the Product Backlog to estimate user stories. These are then committed to sprints where teams break them down and given estimates as a Work remaining value. If the Estimated value is not set in Jira and an item with a Work remaining value is synced from Helix Plan, both the Jira Estimated and Remaining values are set to the Helix Plan Work remaining value. Future updates to the Work remaining value in Helix Plan will not change the Estimated value, but will update the Remaining value. Logged work does not have a corresponding column in Helix Plan and is not synced. |
| Finish | Due (date) | For Helix Plan Task Schedule items. The fields are not populated for QA and Product Backlog items that do not have finish dates. If these items are committed to a sprint, the Jira Due value is set to the Helix Plan Finish value for the sprint they are committed to. |
Adding write access for Jira custom fields
The integration supports adding write access for custom Jira fields in Helix Plan. To do this, edit the integration settings file.