RELATED IDEAS
Reviewer users should be able to change a feature's (or requirement's) up to a certain point
For example, We may have our engineering team (or QA team) in Aha! as "reviewers" and we would like them to participate in escalating status - such as:
Engineer would say "In Development" when they start, and "Development Complete" when done.
Then the engineering managers with contributor rights would take over and validate, ship or send back if need be.
-
ADMIN RESPONSEOct 17, 2014
We do not plan on implementing this as described as it would break our user permission model. However, if you do have this use case and want all of your engineers actively working in Aha! -- we want to hear from you. Please email us at support@aha.io and we can discuss options with you.
I would really like this - we're looking at using Aha as our only ALM tool and pushing approved work directly to GitHub. But it is a bit clunky to have only a small subset of users able to edit/update items at the requirement level; the to-dos are useful but feel like a bit of a workaround.
Hi Brian, thanks for the response. Right now we use Pivotal. But we are thinking about the possibility of consolidating tools into 1 (and PT doesn't do planning very well). But, paying for an Aha! account for each engineer will get costly very quickly.
I would like to learn more about your use case. Are your engineers also using a development specific tool or are they doing all of their work in Aha! Please let us know.