ADD A NEW IDEA

Jira

Showing 245 of 8635

Broken Atlassian Webhook

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date). Unles...
Guest over 5 years ago in Jira 0 Future consideration

Allow parking lot features and releases to not be sent to Jira

I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain over 5 years ago in Jira 1 Already exists

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

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

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

Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited

In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Kevin Burges over 6 years ago in Jira 0 Unlikely to implement

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated Currently, I have three JIRA projects integrated to a single AHA product: LCI TEAM METHD UXH Currently, these three projects show up as Send to JIRA Send to...
Guest almost 7 years ago in Jira 5 Already exists

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest about 7 years ago in Jira 0 Already exists

JIRA integration without admin account rights

At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest almost 9 years ago in Jira 0 Already exists