ADD A NEW IDEA

All ideas

Showing 8935 of 8935

Excel Documents Not Sending to Jira Custom fields

Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
Guest 7 months ago in Jira 0 Future consideration

Better search facilities for notebook documents

Who would benefit? Product teams who use the documents section to capture client information (who the client is, what was discussed on calls etc) What impact would it make? Better search facilities would enable us to get evidence to use to make be...
Guest 7 months ago in Notes 0 Future consideration

Show related Aha entries on the Persona record

Who would benefit? Product Managers thinking about their persona and updating the record What impact would it make? Allow the PM to quickly navigate from the person to, say, the theme or overarching initiative. Currently you can only navigate the ...
Reece H 7 months ago in User story map 1 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer about 9 years ago in Jira 12 Likely to implement

@mentions list from comments that would show under "My work"

I start my day by going to the My Work tab where I see the features and To dos. While I can receive a notification via email of the mention, it would be much easier for me to track conversations that I have been mentioned in if they would show up ...
Guest about 7 years ago in My work 3 Future consideration

Allow multiple persona types to coexist for Products, Product Lines, etc

We need to be able to define multiple personas for individual products or product lines - currently only one template can be used for these entities. In addition to the user personas already in the system, we also need to have Buyer and Enterprise...
Guest over 4 years ago in Application 2 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 5 years ago in Azure DevOps Services and Server 9 Future consideration

New features added to master feature inherit attributes

I'd like to be able to add a new feature to a master feature and have it inherit info like Aha! score, custom fields (e.g. customer, market, initiative), etc.
Elizabeth Karam over 7 years ago in Features 4 Future consideration

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt over 2 years ago in Rally 3 Future consideration

Show multiple pages of a mockup in the image viewer

Currently, when you create a mockup with multiple pages, only the first page is visible in the image viewer. The only way to get around this today is to create multiple mockup files. I would like the ability to show all pages of a single mockup in...
Ron Yang almost 7 years ago in Mockups 9 Will not implement