Ability to attach document after release is shipped/closed
We do post-launch evaluation after a product is released. I'd like to attach that analysis to the release. Once the status of a release is changed to "Deployed," it's Closed and I cannot attach documents.
Analisa Meyer
over 7 years ago
in Releases
0
Unlikely to implement
I have the ability to change the API keys when creating items, but I don't have that ability in the Customs Table section. My only option right now is to delete the table and re-create it. Not a huge deal but a nice to have.
Mike Irving
over 7 years ago
in User management
0
Already exists
Close To-dos when feature status category changes to Will Not Do.
As an Aha! user, I do not need to see To Dos that are children of items having a status category of Will Not Do because I no longer have to do it. The To-dos list on the My Work page should suppress such items that, for all intents and purposes, n...
Tom Beck
over 7 years ago
in To-dos
0
Unlikely to implement
Work remaining estimates for releases on show 'committed' items
For capacity planning it would be very helpful if, for a given release, we had some way to indicate which features or requirements were committed to and base the work remaining and capacity limits off of that value.
Right now, the 'work remaining'...
Provide ability to build a dashboard based off release milestones and phases.
We have several phases and milestones per-release for various activities. I want to be able to generate reports/dashboards of these for multiple products & releases at a time.
Guest
over 7 years ago
in Reports
0
Already exists
Two-factor authentication for the integration Aha! to JIRA
Quoting my mail replying back to Brian deHaaff:
Hi Brian,thanks a lot for the offer to help with my onboarding – the idea to trigger this communication from the Founder / CEO indeed transports a feeling of importance that makes it hard not to resp...
Guest
over 7 years ago
in Jira
0
Unlikely to implement