Track time between Aha! and Jira (integrations 2.0)

With the integrations 2.0 version of the Jira integration, teams can sync capacity between Aha! and Jira for master features, features, and requirements. As with all development system integrations, you will need to be a Product Owner in Aha! to configure time tracking for your Jira integration.

jira-aha-time-tracking.png

How it works

First, you need to have capacity planning enabled in Aha! This is done through Settings > Product > Configure by enabling Planning at the bottom of the page.

If you had capacity planning enabled prior to setting up your Jira integration, the time tracking mappings will already be preconfigured with our default recommendations.

If you did not have capacity planning enabled prior to setting up your Jira integration, you will need to go to Settings > Product and edit your integration's field mappings to incorporate the time tracking fields.

You will then be able to set your integration mappings for master features, features, and requirements to include Estimate — original and remaining — and Work done fields. Linking these fields for all three record types gives you the flexibility to set the estimate at the right level for each work item. The integration supports either time-based or story point estimates.

And don't worry — if you are configuring time tracking with an existing integration, you can use the Update records functionality to pull your estimates from Jira into Aha! for your existing integrated records.

Recommended mappings

When configuring the time tracking field mappings, you will notice various options for each field. The recommended default mapping is to use the Record only fields for both the Aha! and Jira side.

This option automatically accounts for differences in how Aha! and Jira aggregate capacity estimates between parent and child records. In Jira, the total capacity estimate is calculated as the value for the record plus the value of all contained sub-tasks. In Aha!, if you set capacity estimates at the requirement level, the capacity for the feature is the sum of the requirement estimates.

The Record only option will only sync the estimate if the estimate is explicit at the record level. This means if you have a feature containing requirements where the estimates are captured at the requirement level, then the feature's estimate (which would be the total of the requirements) is not sent to Jira. This option prevents issues where the differences between how Jira and Aha! aggregate estimates would cause duplication of estimates.

Aha-jira-capacity-planning.png

Other options

  • Including Sub-tasks: This Jira-side field mapping option is useful if you do not have sub-tasks mapped in your integration but wish to visualize estimates related to sub-tasks within Aha! It will take the aggregate estimates of all Jira sub-tasks plus the Jira standard issue and send that through to the corresponding Aha! field.
  • Including estimates calculated from a child record: This field mapping option from the Aha! side is primarily useful in situations where you are performing estimates at the child record level in Aha! but not syncing the child records themselves to Jira. For example, if you were to perform estimation in Aha! at the requirement level but only send the feature to Jira, you would need to use this option to ensure the calculated estimate from the requirements is sent to Jira through the Aha! feature.

 


Was this article helpful?
2 out of 2 found this helpful