Allow Jira to update the status of releases in Aha

A little bit like the compliment to APP-I-1193.

We create releases in Product Management, and then send them to Jira when they're ready for development. Product Management tracks the release status in Aha.

Unfortunately, when development marks the release as "released" in Jira, nothing happens in Aha. This feature proposes that when the release is marked as "released" in Jira, the release is marked as "Ready to Ship" in Aha. This would trigger Product Management to do whatever is required to get it to the "Shipped" state.

Right now, it's a bit of a pain, because the release needs to be manually updated in 2 places.

  • Jason Slaughter
  • Jun 30 2015
  • Will not implement
Release time frame
  • Attach files
  • Tamer Sabry commented
    August 08, 2015 08:17

    This is needed to track what has shipped in jira automatically 

  • Tamer Sabry commented
    August 30, 2015 17:01

    Any update on getting this one? 

  • Admin
    Brian de Haaff commented
    September 02, 2015 17:34

    Shipping a release in Aha! is a big deal as you know. It marks the features that are shipped as shipped and automatically moves features that are not done into the next release. It seems like requiring an extra step to come back to Aha! by PM and consciously mark a release as shipped is the right behavior here. Otherwise, there is a good chance that things are going to go very wrong and create a mess. I also suggest that for most customers the "Release" in Jira is not equivalent to a full market release which they are planning in Aha! It may even have non-dev oriented features. It is often a sprint or some breakdown of technical work. So, we are reluctant to add this capability. And even if we did, it would require a ton of configuration options starting with status mappings and then controls on which system would update the other. For all of the reasons above, which we hope you can understand, we are not going to plan to implement this at this time. 

  • Snap Kitchen commented
    December 18, 2015 21:15

    Brian, I'd respectfully disagree with your response.  First, the submitter did not ask to take the act of releasing out of the PM/aha hands.  He merely asked for the status to update to "Ready to Ship" based on the visibility into JIRA.  

    Second, you're answer also dictates to your customers how they should handle releases.  The rest of aha appears designed with a "customers do lots of different things" approach.  Why not for this request?


    Scott Brittain