Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 269

Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete

These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
Marcie Gardner about 3 years ago in Jira 2 Future consideration

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest over 5 years ago in Account settings / Jira 1 Future consideration

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest almost 6 years ago in Jira 0 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet about 6 years ago in Jira 1 Future consideration

Auto-sync of sprint field between JIRA and Aha

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confus...
Guest over 6 years ago in Jira 2 Future consideration

If a comment is deleted in Jira, please delete that comment in Aha! also

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes about 7 years ago in Jira 1 Will not implement

Include JIRA records in linked records

We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
Guest over 8 years ago in Jira 2 Unlikely to implement

Add 'Send to integration' automation action for Aha! Ideas <> Jira integration

What is the challenge? As PMs review ideas submitted to Aha! there may be ideas that need to be sent directly to Jira — thinking about bugs that are reported through an ideas portal. What is the impact? Those ideas need to be reviewed alongside al...
Justin Waldorf 7 months ago in Ideas / Jira 0 Future consideration

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.
Guest almost 2 years ago in Jira 1 Likely to implement

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black over 2 years ago in Jira 1 Future consideration