ADD A NEW IDEA

Jira

Showing 168

Capability to tag JIRA users

As a user with an integration with JIRA, I want the ability to @ users in my feature, requirement, or comments in Aha and the @ will sync to the JIRA users available so they can receive a JIRA notification. Our dev team does not use Aha notificati...
Guest almost 6 years ago in Comments / Notifications / Jira 0 Future consideration

JIRA Integration - allow bidirectional mapping of the "time frame" field

for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
Alan Valentine almost 6 years ago in Jira 1 Future consideration

Ability to map Jira's "Team" to a custom field in Aha!

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible
Guest about 6 years ago in Jira 10 Future consideration

Ability to configure integrations not to create new records in Aha

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
Kevin Burges about 6 years ago in Jira 0 Future consideration
140 VOTE

Sync record's workspace, goal, initiative, epic, and release (name and link) to Jira

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker about 6 years ago in Jira 8 Future consideration

Link user stories (requirements) in JIRA when under the same epic (feature)

We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
Elizabeth Karam about 6 years ago in Jira 2 Future consideration

Webhook error handling with Jira integrations

I spend countless hours trying to debug webhook issues only to find the error should have been easily caught and reported back correctly. It seems the only issue that comes back is "Processing webhook: unhandled error. Please contact support@aha.i...
John Paul Grippa about 6 years ago in Jira 0 Future consideration

History of items created via integration

In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them. A modal notification like you currently use would work at a one-by-one level. If that makes sense. Even better would be a tab in ...
Max Cascone over 6 years ago in Jira 1 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.In 2...
Danny Archer over 6 years ago in Jira 3 Future consideration

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Guest over 6 years ago in Jira 1 Future consideration