RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-3348 Promote an idea to a feature requirement.
Convert Idea to Requirement (instead of convert to a feature)
Merged
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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
Agree - seems like the same thing as https://big.ideas.aha.io/ideas/APP-I-3348
Very valuable enhancement.
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)
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.
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.
Ideas come in all shapes and sizes, so I would like the ability to Promote an Idea to anything - feature, launch, requirement, etc.