Looking to submit a support request? We are now a Perforce company, please submit any requests on our new support page.
Follow

Column matching

Hansoft JIRA integration columns and matchings

JIRA columns created in Hansoft by the integration are appended with (JIRA) to be easily distinguishable. Similarly all Hansoft columns created in JIRA are appended with [Hansoft]. Project specific Hansoft columns will in addition to the Hansoft tag have their project name in square brackets as well.

Example: "Database ID [Hansoft, Support project]"

Summary fields for numeric columns

In order for the integration to properly work with summaries, all numerical Hansoft columns will generate two additional fields in JIRA: Stat and Summary. These columns should not be deleted or updated manually. The option to enable the Summary and Stat columns are set up per integration in the sync settings dialogue.

More information found here.

 
Example: Estimated Ideal Days [Hansoft Stat]

URL columns

The integration makes URL columns available on both the JIRA and Hansoft side to make it easy to jump between items in the two systems. In Hansoft this column is called "JIRA URL (section name)" and the corresponding column in JIRA is called "Item URL [Hansoft, Project name]".

URL in Hansoft:

URL in JIRA:

Note: In order for the Hansoft URL:s to be properly generated the server hostname must be specified. This option is found in the Administration tab in Hansoft.

JIRA attachments default column

When the integration is running a column will be available in Hansoft by default which contains links to the attachments of a synced item. This column is called "Attachments (JIRA, Hansoft section)". These links can be used to quickly jump to attachments stored on the JIRA side.

 
In addition to this column the integration has a functionality to easily download all attachments of a synced item for storage on the Hansoft side. This is described in more detail here: Migrating attachments

Specific column matching

As described above all system specific columns will be created and available for use in the two systems. There are a couple of core columns that are directly matched between the two systems however and they are described in more detail below. The two columns associated with assignment and work remaining have some logic associated with them whereas the other four columns are simply matched.

1.Hansoft "Assigned to" - JIRA "Assignee"
For single user assignments the two columns are simply synced between the two systems.
 
Hansoft supports multiple assignees whereas JIRA does not. In order to support this the "Assigned to [Hansoft]" column in JIRA is used. The "Assigned to [Hansoft]" column in JIRA contains a list of all the assigned users from Hansoft. The first user in that list will be set as "Assignee" in JIRA. Using the "assign to" functionality in JIRA will update "Assignee" and add a single user in the "Assigned to [Hansoft]" list, clearing the other assignees in the list. If you wish to use multi assignment from JIRA you must use the "Assigned to [Hansoft]" field to assign users.
 

2.Hansoft "Work remaining" - JIRA "Logged work", "Estimated", "Remaining"
 
Estimation works differently in Hansoft and JIRA. In Hansoft "Estimated ideal days" or "Points" are used in the Product Backlog to estimate User Stories. These are then committed to Sprints where the teams break them down and give them estimates on "Work remaining". Since there is no 1-1 connection on how this works in the two systems it is setup as below.
If "Estimated" is not set in JIRA and an item with "Work remaining" is synced from Hansoft, both "Estimated" and "Remaining" will be set to the "Work remaining" value. Following updates to "Work remaining" in Hansoft will not change "Estimated" but will only update "Remaining".
"Logged work" does not have a corresponding column in Hansoft and is not synced.
 
Tip: In JIRA you have the option to set the format of the "Remaining" field. Since Hansoft uses hours as base value for "Work remaining" it is recommended that you set hours in JIRA as well to avoid confusion. This option is found under "Issue Features" in the "System" tab of JIRA.



 

3.Hansoft "Item name" - JIRA "Summary"
Simple match.

4.Hansoft "Comments" - JIRA "Comment"
Simple Match

5.Hansoft "Originally created by" - JIRA "Reporter"
Simple match

6.Hansoft "User story / Detailed description" - JIRA "Description"
Simple match

7.Hansoft Finish - JIRA Due date
For Task Schedule items synced to JIRA "Due date" will be matched with the Hansoft "Finish" date. For QA or Product Backlog items, which do not have finish dates of their own, this is not populated. If these items are committed to a sprint the JIRA "Due date" will be set to the Hansoft "Finish" date of the sprint they are committed to.

 

Adding write access for JIRA custom fields.

The JIRA integration supports adding write access for custom JIRA fields in Hansoft. This is done by editing the JIRA integration settings file. First you need to know the full path to the custom field that you want to add, including the plugin key (e.g <full.plugin.key>:<customFieldName>). Second, decide what type of Hansoft column the field should be mapped as. The possible types are "Text", "Hyperlink", "DropList", "Integer", "Float", "DateTime", "MultiLineText", "People", "TimeSpent", "MultiSelectionDropList", "DateTimeWithTime". You also need to set the initial access right when the column is created, possible values are "AllProjectMembers", "SubAndMainProjectManagers". "MainProjectManagers", "ReadOnly". The access rights can later be changed in the "Customize columns" settings in Hansoft.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request