RELATED IDEAS
Provide tools for Change Control
Once development on a release is underway, things happen. Change Control should encompass approvals and permissions to edit dates and schedule, and rollback. Here are some requirements:
1. A product owner (or an "uber product owner", e.g. the VP of Products) "Starts" the release - by pressing a button e.g. "Start Release"
2. Once the release is started Features and Dates cannot be edited without a proposal (from anyone) and an approval (by a product owner, uber product owner, or consensus of several product owners).
3. The change is versioned and can be rolled back.
4. The change can be displayed with edit markup that looks like track changes or suggestion mode in a word processor.
-
ADMIN RESPONSEJan 8, 2016
Within Aha!, there are 4 types of user roles and permissions (product owners, contributors, reviewers and viewers). We've gathered much feedback from the community in coming to this place for the user types.
We are unlikely to make additional updates in the area of permissions, particularly in regard to specific additional controls that users have and do not have. These areas are workflows which we feel should be commissioned outside of Aha!, where the team member is aware of the areas in which they are "allowed" to revise vs. not.
We hope you can understand.
2
MERGED
Approvals prior to sending to development tool.
We really need a way to "Check" a box that only the "Assigned Owner" of the todo could check as part of the workflow transitions. Ideally there would be a way to set up Aha so that when a release or feature is "Sent to development" it goes into a ...
0
Unlikely to implement
2
MERGED
FDA Electronc Signature Approval & Change Control
See my support request....Requirements need to be reviewed and approved by a defined group of roles. The tool needs to allow for electronic signature that supports 21 CFR Part 11 requirements. The tool cannot allow the requirement to be changed wi...
0
Unlikely to implement
Please revisit this idea.