Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 242 of 8277

Allow Jira Integration to synchronize External Release Dates

In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.
Guest 5 months ago in Jira 0 Future consideration

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest over 8 years ago in Jira 4 Unlikely to implement

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 7 years ago in Jira 11 Already exists

Improve integration job troubleshooting steps

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...
Alfred S over 1 year ago in Jira 0 Future consideration

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 over 4 years ago in Jira 2 Unlikely to implement

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest over 8 years ago in Jira 9 Future consideration

New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration

There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin over 1 year ago in Jira 0 Future consideration

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller almost 2 years ago in Jira 0 Future consideration

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest over 8 years ago in Jira 2 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 over 4 years ago in Jira 0 Future consideration