Convert Idea to Requirement (instead of convert to a feature)

We map features to epics in Jira, a requirement is often tied to a direct use case. Often, these use cases will pop up in Zendesk from a customer inquiry and will be very well documented there. It's great to be able to immediately create an Aha idea to capture the entire history in one click. I want to be able to convert that idea into a requirement of an existing feature instead of making a new feature out of it.

  • Guest
  • May 7 2015
  • Likely to implement
Release time frame
  • Attach files
  • Max Cascone commented
    August 10, 2015 21:39

    Ideas come in all shapes and sizes, so I would like the ability to Promote an Idea to anything - feature, launch, requirement, etc.

  • Shri Iyer commented
    August 26, 2016 03:23

    While the 2 step process works, what actually happens during a conversion to a requirement is that the link between the idea and the feature/requirement breaks. Aha should maintain the link between the converted requirement and the idea. Else the idea owner/filer won't be able to monitor the status of the idea.

  • Josh Davidson commented
    July 20, 2017 15:24

    I echo what Shir has said. Ideas that are converted to features then requirements lose the link to the original idea. Seems like an oversight.

  • David Goodwin commented
    March 13, 2018 15:45

    Agree. I would like to convert an idea to a requirement and maintain a link between the requirement and originating idea. In fact, I would like to see a hierarchy maintained where many ideas may be attributed to a requirement. Our Jira integration uses features for epics and requirements for stories. The development teams concern themselves with the creation of tasks and sub-tasks in Jira (tasks and sub-tasks are considered part of the development domain, not the business domain)