RELATED IDEAS
Ability to prevent promotion of ideas to a specific record type
Currently, when promoting an idea, you can promote it to an Initiative, Master Feature and Feature.
It would be useful if you could restrict this for some Ideas Portals. For example, if you managed all large initiatives via one portal, you would not need the option to promote ideas to master features or features.
In our company we have only enabled Initiatives and Features in Aha! Roadmaps. Therefore, it would be beneficial to streamline the process of promiting an Idea by limiting the available choices to Initiatives and Features, rather than displaying the full array of options, which includes INitiatives, Epics, Features, and Requirements.
I echo previous comments for this idea. We are all trying to use Aha to support our company processes, which lead us to use tools like Aha in certain ways.
We would like idea promotion to be restricted to initiatives and epics (not Aha requirements) in order to support our quality system and tool validation requirements.
We can work around this by training users not to do it, but it would be far better to configure this to enforce compliance.
Hey there. I'd like to endorse this 100%. We at CCP Games are setting up a development process in which it happens to be the case that we only ideas to be promoted to a particular type (in our case initiatives). What is guaranteed to happen in a large production is that people will make mistakes if the system doesn't prevent them. So not having this feature means that people have to spend time trying to prevent, then monitor any mistakes and communicate when mistakes happen. I'd love for us to spend valuable time in a different way!
Jaggaer would like to restrict promoting Ideas to Features only to manager the risk of customer service employees who triage ideas creating strategic initiatives and epics