ADD A NEW IDEA

Jira

Showing 248

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 8 years ago in Jira 0 Already exists

"Do you want to sync features as well?" (for Jira/Aha integration)

In my organization we need to sync features and releases in Aha to two different Jira projects. One project receives 100% of the features and releases - perfect 1:1 sync. But the other project is only for features that rely on the design team. So ...
Byrne Reese almost 4 years ago in Jira 3 Unlikely to implement

Show Integration Errors Next To Integration Link

So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
Guest about 4 years ago in Jira 0 Future consideration

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 8 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 8 years ago in Jira 0 Unlikely to implement

Make fixed workflow transition enforcement optional for Jira integratations

Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it. With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need...
Daniel Hirschberg over 4 years ago in Jira 0 Future consideration

Change Button Click to Dropdown for Integration Screen

When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
Josh Tambor over 4 years ago in Jira 0 Future consideration

Features assuming the same release as its parent master feature when importing from Jira

Given that I have an epic in Jira, linked to a Master Feature in Aha And the Master Feature is found in "Release X", When I create a story beneath that epic in Jira, Then the story should be imported as a child to the Master Feature, AND ass...
Guest over 4 years ago in Jira 0 Future consideration

Working with JIRA worklog dimension (worklog date)

Dear aha, in order to resolve reporting of time spent on features within specific timeframes, it might be useful to think about including worklog date of JIRA issues into synchronized aha backlogs. This would enable creation of reports where not o...
Daniel Pokrývka over 4 years ago in Jira 0 Future consideration

Allow Feature or Master Feature to be pushed to Jira when the Aha! state is mapped but blocked when it is un-mapped

Our product management team wants to plan features prior to making the feature available via Jira Integration. For example while a feature is under consideration or in planning/grooming state it would only exists in Aha. Once the feature is ready ...
Guest over 4 years ago in Jira 0 Future consideration