Re-enable conversion of Features to Requirements when JIRA integration is active

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously it’s been fairly easy to clean this up as you can convert each Feature to a Requirement in Aha under the correct Feature, and this change would be reflected in the linked JIRA story (the Aha reference would be updated). However since the update in June ( this is no longer possible, and requires a somewhat lengthy and tortuous manual resync between Aha and JIRA to get the issues linked correctly. It would be massively helpful and remove a lot of frustration for project admins if the Feature to Requirement conversion feature could be re-enabled when the issue is integrated with JIRA, while taking care to avoid the potential data integrity problems that were identified that triggered this change in the first place.

  • Mike Ward
  • Jul 20 2016
  • Shipped
Release time frame
  • Attach files
  • Karsten Linzmeier commented
    July 22, 2016 08:38

    Is there any indication as to why Aha! decided to change this feature in the first place?

  • Mike Ward commented
    July 23, 2016 01:02

    Thank you for the fast response. Two questions:

    1) We have never experienced corruption of our Aha to JIRA integration due to this feature, so I'm curious as to what actually happened and why?

    2) For this new feature, what is the expected timeline for implementation, and once implemented will this either allow Requirements created on their own to be added later to Features in Aha, and/or will it be able to follow stories in JIRA that are moved in JIRA into Epics?

  • Shri Iyer commented
    July 25, 2016 21:43

    Maintaining the data integrity and forcing the aha user to first change it in JIRA and then convert in Aha is ok. But to not allow the conversion at all is painful. Please re-enable this feature.

  • Admin
    Chris Waters commented
    July 29, 2016 23:14

    We do pay attention to the votes, even when they are mostly from the same company :-). We have re-enabled this capability while we work out a better solution.