Allow features to span across releases for better data model alignment between Aha and JIRA

Please allow features to span across releases for better data model alignment between Aha and JIRA.

Both Aha and JIRA have 3 levels in data model. Aha focusing on Why-What has Goals-Initiative-Features and JIRA focusing on What-How has Epic-Story-Sub-Task. The bridge between the two systems is Feature to Epic and both these need to span across sprint releases since these are higher level than story. Stories may be too details for Aha and difficult to consume by stakeholders. Mapping initiative to epic limits the use of initiatives which can have multiple epics. If the Features can span across releases then it will be easier to map the two systems and also use this level in data model for SAFe program board. 

  • Karthik Rajagopal
  • May 12 2017
  • Will not implement
Release time frame
  • Attach files
  • Admin
    Austin Merritt commented
    May 15, 2017 14:37

    Hi Karthik, thank you for the idea. We recently introduced a new object within Aha! called Master features. Master features are perfect for capturing epics. Using master features as epics, you can then use features as stories which can be delivered incrementally over a series of releases. With this in mind, I am going to mark this idea as Will not implement. However, we do have another idea that is Planned to add support for Master features to the JIRA integration. I would recommend that you vote or subscribe to that idea so you will be notified of any updates:  Thank you!