Hansoft/JIRA comparison (differences)

Before going into more details regarding the integration it is important to explain the main differences between Hansoft and JIRA regarding projects, data models and so on.

Item type, status and workflow differences

Items and tasks in JIRA and Hansoft differ in regards to type, workflow and statuses. All item types in JIRA are associated with a workflow and their item status is derived from that workflow. Items in Hansoft are defined by the section from which they originate.

Items in Hansoft from the product backlog are neutral in the sense that they only exist in the product backlog and can be typed as "user stories". Items in the Product Backlog can be committed to the project schedule where they can be task scheduling items and be planned out gantt style, or they can be committed to sprints and be estimated as agile items. Theses items do not have a workflow attached by default in Hansoft.

Items in the QA section does however always have the defined QA workflow applied.

Because of this difference, one important step in setting up your integration is replicating the JIRA workflows in Hansoft for the item types which you are going to sync, so that the workflows can be properly applied and matched when running the integration. Workflow matching is described in more detail in the installation part of this manual.

You can read more about workflow creation in Hansoft here: Creating matching workflows

Hansoft sections vs JIRA screens

Hansoft projects contains three main views where tasks and items are located; the product backlog, the project schedule and the QA section (see screenshots at the bottom of this page).

The section that mostly resembles JIRA is the QA section which is a flat structure of items (bugs). Items in the QA section always have an assigned workflow which makes this section easy to map towards JIRA.

The product backlog and project schedule within Hansoft are hierarchy based and supports a virtually unlimited tree depth. JIRA items are organized in a flat structure with sub-tasks supplying a hierarchy of depth one.

Because of this difference in data structure, a thorough mapping of the two systems is needed when creating the JIRA filters and Hansoft reports used for syncing items. This is described more in detail in the Detailed installation instruction section of the manual.

JIRA and Hansoft projects

In a typical agile project we have our product backlog for planning and estimating tasks, the project schedule where we work on tasks and a QA section where we handle bugs and issues during development. In JIRA these items are of different types but stored in a flat structure. When integrating with Hansoft we most likely want the different item types to be synced to the different sections of Hansoft (see the above section).

You need to setup the integration for each Hansoft project section that you want to sync items to. In each section you create a report to filter out the items you wish to sync (picture 2). If you are syncing three different JIRA item types to different sections in Hansoft you need to create three JIRA filters, one for each item type (see piscture 1).

Picture 1: JIRA filters syncing different item types to different sections in Hansoft

Picture 2: one report per section is used in Hansoft to specify which items that should be synced to JIRA

Picture 3: in this setup we sync two Hansoft sections to one project in JIRA and another Hansoft section to a second JIRA project

Hansoft sections

Project schedule view


Product backlog

QA section

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