Sync capacity estimates between Aha! and Jira (integrations 1.0)

This support article refers to the historical 1.0 version of the Aha! integration with Jira. Capacity estimates are NOT currently supported in the new integration. If you are using the 2.0 version of our Jira integration, reference this article.

The Jira integration supports syncing either story point or time based estimates between Aha! and Jira. This is a valuable part of the integration for any team looking to create high level estimates in Aha! and then allow the development team to take those estimates and update them with actuals once they start working.

Additionally, when syncing time based estimates work logged against the estimate will automatically reflect back into Aha! as logged effort on the Aha! record. This allows the product team to keep up to date with progress in Aha!

How it works

First, you will need to go into your product settings in Aha! and enable capacity planning. This is located under Settings > Product towards the bottom of the first page.



Note: If you plan to sync estimates between Aha! and Jira you want to perform this step before importing any records into Aha! from Jira. Failure to do so can result in 0s being sent from Aha! to Jira as Aha! will default to have no value for estimates when this option is initially enabled. Aha! cannot undo this, you will need to roll back your Jira server or manually fix the estimates by going through your Jira history.

Once you enable planning in Aha!, you can select between having the estimates associated with Features or Requirements. This is particularly important for the integration because of differences between how Aha! and Jira fundamentally handle estimates.

Aha! aggregates estimates from the requirement to the feature. This means if you have two requirements, each with 5 points of effort associated with them, your feature will have a total of 10 points of effort.

Jira does not work this way. In Jira the story points for the Epic and the User Stories are added together. An Epic can have 20 points of effort while the two stories contained in the Epic each have 5 points - the total effort for the Epic and User stories would then be 30 points. 

This causes a data mismatch between the two systems. To remediate this, Aha! only syncs Feature or Requirement estimates based on if you enabled estimates for Features or Requirements in your account.

  • If you enable it for Features, changes to the Jira User Story estimates will have no impact on Aha!
  • If you enable it for Requirements, changes to the Jira Epic estimates will have no impact on Aha!

With the Aha! configurations set, you can now import your Jira records and you will see any estimates that existed in Jira automatically populated into Aha!

Inflated estimates being synced?

For this integration, Aha! assumes that the default time tracking value of minutes is configured in Jira. If you have a different value configured in Jira you will see inflated estimates synced between the two systems when syncing time based estimates.

To resolve this, you will need to change your Jira configuration as described in the above linked document.

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