ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 231

Allow integration of Custom Fields to any Jira Field of a supported field type

We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field. We would like to push this custom field valu...
Guest over 5 years ago in Jira 0 Already exists

JIRA and Aha synchronized numbering

We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
Guest about 6 years ago in Jira 0 Unlikely to implement

Keep unsupported 3rd party Jira tag as it is upon syncing

In Jira, it is possible to render Gherkin by using 3rd party plugin. After modify the description field in Aha! and synced with Jira, the format is ruined by Aha!. Original Description on Jira:{code:gherkin} Scenario: The empty state text sh...
Guest over 6 years ago in Jira 0 Future consideration

Need an option to sync Jira fixVersion "Name" instead of "ID"

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
Guest almost 7 years ago in Jira 0 Already exists

Link to Multiple JIRA Items

On some occasions we will end up with multiple JIRA tickets for the same item in AHA. We'd like to be able to track each of these in Aha, but most importantly be able to pull the time tracking data into aha across all of the tickets.
Guest about 7 years ago in Jira 2 Unlikely to implement

Sync @ Mentions With Linked JIRA Users

Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations. I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ m...
Ryan Schultz about 7 years ago in Jira 0 Unlikely to implement

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest 6 days ago in Jira 0

Use Custom Table data in Integration with Jira

Need to functionality to include Custom Table fields in the integration mapping. We created a new table for Aha Roadmaps for Program Increments. The table is linked to both Epics and Features, to simplify the reports (same value for both). The cha...
Edgar Holguin 15 days ago in Jira 0 Future consideration

Manual Sending of Requirements to Jira

Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R about 1 month ago in Jira 0 Future consideration

Allow Mapping of Requirement Type from Jira to Aha!

Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
I R about 1 month ago in Jira 0 Future consideration