Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8815

Set feature rank directly

Drag and drop is onerous only available in full release view. User should be able to directly enter rank position (or even before/after another ticket reference.)
Guest about 8 years ago in Features 13 Future consideration

Updating of Feature dates should automatically adjust dates of features with downstream dependencies

Summary: This comes from a project management use case where a team manages a set of activities/tasks through Features for a project and the activities have a very sequential delivery with fixed offsets between each activity. The plan starts off...
Matt Case over 7 years ago in Features 10 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer over 8 years ago in Jira 15 Future consideration

Integration with MS project

It would be great to tie into MS project for the high level milestones and phases so as either is updated....it would update the connection.
Guest over 7 years ago in Wanted 10 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The i...
Matt Case about 8 years ago in Jira 13 Future consideration

MS Planner integration

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
Guest about 5 years ago in Wanted 8 Future consideration

Expose Watchers field for reporting

In the organisation we are deploying Aha for, there are over 100 products. Features are built across the products. Programme managers use initiatives to track the delivery of a master feature. If a feature is associated a master feature, or an ini...
Project Parker about 6 years ago in Reports 7 Future consideration

Threaded comments

As comments are made on a feature, sometimes there are questions that come up that are unrelated to the other comments that have been entered. It would be much easier if I could just reply to the comment and the thread is kept/read in that fashion...
Guest about 7 years ago in Comments / Notifications 10 Future consideration

Prioritization view: option to export to Excel

We gather feedback on priorities from various stakeholders, including many who don't have edit access in Aha! (owners/contributors). Excel is something that everybody knows, so it’s easy to send around to stakeholders and gather feedback. You can ...
Dale Potter over 1 year ago in Reports 2 Future consideration

Determine default Home Page for All Users

When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
Matt Howard over 6 years ago in Account settings 8 Future consideration