Skip to Main Content
ADD A NEW IDEA

Jira

Showing 249 of 8735

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham about 5 years ago in Jira 2 Unlikely to implement

Allow users to refresh all Aha! features from a linked JIRA integration.

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow over 8 years ago in Jira 0 Already exists

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 5 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 5 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 confu...
Guest over 5 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 6 years ago in Jira 1 Will not implement

Ability to update a file attachment of a feature and update in the linked record of JIRA as well

Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda over 6 years ago in Jira 1 Future consideration

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 7 years ago in Jira 2 Unlikely 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 1 year ago in Jira 1 Future consideration

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black over 1 year ago in Jira 0 Future consideration