Not every customer wants to leverage requirements in Aha. For example, here at Intelligrated (a Honeywell company), we are doing roadmap planning at the portfolio level in Aha. What that means is that we create and track Epics (Features in Aha) in backlogs and them plan releases accordingly. We push those Epics down to JIRA where the teams who are executing create Stories. For our process to work, we do not want any Requirements (stories) entered in Aha. They have to be entered in JIRA only, otherwise it skews our Aha reporting and burndowns. We purposely have integration at the Feature level but not at the Requirement level.
For this to work, we need the ability to restrict creation of Requirements. Right now it is wide open and anyone who can create an Epic can also create a Requirement. We would like to see the ability to control this and restrict creation by permissions at the user level. Even more helpful, would be at the Role level.
|Release time frame|
Thank you for the request. We have some levels of permissions today where its possible to prevent Reviewers and Viewers from creating objects in Aha! (though these includes features, requirements and all other objects).
At this time, we do not have plans to make updates in this specific area to restrict creation of Requirements based on current priorities and historical feedback.
We would suggest letting your users know that Requirements should not be used in Aha! This could be done by alerting your team through a system broadcast (accessible in Settings -> Accounts - Configure broadcasts). This would appear in the header when users log in so that they are aware of the process. While we understand that this would not completely enforce the actions, it may help.