Skip to Main Content

My ideas: Jira

Showing 31

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

"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 about 4 years ago in Jira 3 Unlikely to implement

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

JIRA integration: support mapping of “Release name” into custom field

Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versi...
Florian Kette almost 6 years ago in Jira 1 Unlikely to implement

Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query

Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc. Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha. Requirement: The query should bring...
Guest almost 6 years ago in Jira 0 Unlikely to implement

Integrations 2.0 - Only show valid integration directions for Release <-> Fix Version

Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version. I had opened ticket because I could not connect to the Jira version using Actions > "Link with existin...
Guest over 6 years ago in Jira 0 Unlikely to implement

Two-factor authentication for the integration Aha! to JIRA

Quoting my mail replying back to Brian deHaaff: Hi Brian,thanks a lot for the offer to help with my onboarding – the idea to trigger this communication from the Founder / CEO indeed transports a feeling of importance that makes it hard not to res...
Guest over 7 years ago in Jira 0 Unlikely to implement

Features linked to JIRA tickets should have JIRA in control of status

When I have a feature linked to a JIRA and a few requirements also linked to JIRAs my expected result is that fields linked with JIRA are controlled by the data in JIRA. For example, if I close all of the requirements within the feature but the JI...
Guest over 8 years ago in Jira 0 Unlikely to implement

Allow tracking simultaneous tracking of both Feature-Level and By-Requirement estimates

The current AHA/JIRA estimate integration allows feature level OR requirement level estimates, however as we don't use JIRA for time tracking we want to use JIRAs 'Original Estimate' field with AHA's per-requirement estimates. My suggestion would...
Guest over 8 years ago in Jira 0 Unlikely to implement