Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 265

Improved error message on incorrect JIRA record type link

Using the JIRA 2.0 integration, if you try to link to an existing record type that is not mapped in the integration config, the error message is very unhelpful. It just says "system error - contact Aha support if this persists" (or something like ...
Mat Wood over 5 years ago in Jira 0 Future consideration

Ability to search on the Jira Key

We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
Guest almost 6 years ago in Jira 1 Already exists

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest almost 8 years ago in Jira 0 Already exists

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Guest about 4 years ago in Jira 3 Already exists

Feature Email update notification to include link direct to Jira record

From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
Scott C about 6 years ago in Jira 0 Future consideration

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter about 4 years ago in Jira 0 Future consideration

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe about 4 years ago in Jira 0 Future consideration

Update Jira integration when Jira custom fields were added

It looks like if you add a custom field in JIRA, Aha will not recognize it unless you delete the integration and add a new one, which means you need to relink everything. You should be able to go through the integration UI and add new field mappi...
Christian Stark over 6 years ago in Jira 1 Already exists

When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration

I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA. I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required. When I perform an import from developmen...
Justin Woods over 4 years ago in Jira 2 Future consideration

Hover text on Jira integration to show project & board

In workspace settings, once an integration is established, it would be nice to be able hover over the integration and see at a glance the project and board without clicking into the integration and looking at the project/board setup.
Guest over 2 years ago in Jira 0 Future consideration