Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
Danielle A
over 2 years ago
in Ideas
2
Future consideration
We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
Automations offer great potential to alert owners/interested parties of action, but are frustratingly limited by the absence of a time based trigger. In our case we want to conform to an SLA in processing ideas we receive and actively sending a re...
Nigel Lawrence
over 2 years ago
in Ideas
4
Future consideration
My agile development team uses story points for estimation. Once work is in progress, I want my developers to log work in time. This helps me understand where their time is going, and to inform future estimates for planning.
Jeff Tucker
over 2 years ago
in Capacity planning
1
Future consideration
I'm a member of the IBM RFE team - data architect. As a downstream data consumer of AHA REST API data I don't know when ideas have been deleted. There is no active 'this idea has been deleted' indicator. Therefore, in my downstream data I have to ...
Guest
over 2 years ago
in Ideas
0
Future consideration
We are storing a client name on user stories and bugs in ADO and it would be great to be able to be able to sync this field between ADO and Aha! using the organization field that has now been made available to all Aha! objects (and not only ideas)...
Nicolas Andrillon
over 2 years ago
in Integrations
0
Future consideration
Easier way to create relationships between Features.
We have fund that creating relationships - Related To - between features is very value but I found myself not doing it because it feels cumbersome...and that's bad. I would live some sort of drag-n-drop a feature onto another feature and having th...
Guest
over 2 years ago
in Features
0
Future consideration
Our organization doesn't need the added hierarchy of initiatives. We want to remove the option to promote an idea to an initiative, so users of our workspaces won't accidentally do so.
Asim Dhital
over 2 years ago
in Ideas
0
Future consideration