Skip to Main Content
ADD A NEW IDEA

Application

Showing 7142

Add REST API to modify paid seats and simplify account provisioning

I do create reviewer and product owner users in aha.io automatically via the REST API. If I create a product owner and this exceeds the current available paid seats I get an exception. It should be possible to read the amount of available paid sea...
Guest almost 7 years ago in Features 0 Future consideration

Add Units and Suffix/Prefix to a Scorecard (Aha! Score)

In creating the metric inputs you can add the units and a prefix eg. £ But when you create a Scorecard itself (which I do to work out number of Resource (Slider) * Days (Slider) * Cost (Fixed per Resource) the output is in £/$ but the scorecard is...
Paul Mundy almost 7 years ago in Features 0 Future consideration

Add a note field for Admins for Layouts (like there is already for Workflows)

As an Aha Admin, I find myself building several different flavors of Layouts and Custom Tables. When I come back (say) 6 months later, I don't the details as to why I created a certain Layout/Workflow or who may have asked for that particular conf...
Joe Carpenter almost 7 years ago in Account settings 0 Future consideration

Allow the people doing the work (designers and developers) to update feature status.

THIS! https://medium.com/@mkhoury/aha-a-few-quirks-in-my-favorite-product-management-software-8eb515fd9e78 My team and I just started using AHA! integrated with Pivotal and I couldn’t agree with you more on this limitation. The people working on ...
Guest about 7 years ago in Application 1 Will not implement

Change default option for Promoting a Idea to Feature

We would like to have the other radio option selected when promoting an idea to a feature, as we rarely promote an idea directly to a feature. Having this option selected makes it more time consuming to promote ideas to existing features.
Guest about 7 years ago in Application 0 Unlikely to implement

Release-less Features

As we evolve towards a continuous workflow, the concept of the Release becomes redundant. Yes, there should be a difference between Deployment and Release, but we still want to Release at the Feature level, if possible. So requiring Features to be...
Max Cascone about 7 years ago in Features 0 Unlikely to implement

Separate Master Release Status and Release Status in feature roadmaps

Currently when I enable Show Release Status in a feature roadmap, it shows both the Master Release and sub-releases's statuses. This is quite noisy. I would like the option to choose one or the other (or both) release type's status to show.
Max Cascone about 7 years ago in Releases 0 Future consideration

Prompt for Reports "Are you sure you want to save over this report?"

I know that we can choose whether or not to have Reports be collaborative and allow them to be saved over by others, but sometimes we need others to be able edit reports, but they need to make sure that they are saving over a report on purpose. A...
Guest about 7 years ago in Reports 0 Future consideration

Make goal status dependent on the status of its initiatives

Then, make initiatives status dependent on the status of its releases... This will just save us some time. When we change the status of a goal, this is based on the status of its associated initiatives. There will need to be some customisation a...
Alex BERRY about 7 years ago in Strategy 0 Future consideration

Maintain context across Features and Releases etc

When editing or viewing a feature for example then selecting the release "tab" a completely different release appears. Meaning you have to find and select the correct one each time. Selections should maintain the context across tabs as you usually...
Dave Tucker about 7 years ago in Features 0 Future consideration