Skip to Main Content
ADD A NEW IDEA

Jira

Showing 246 of 8641

Prevent "roadmap drift" by displaying JIRA Epic labels next to Aha! Requirements.

This idea is a proposed work-around to this problem: https://big.ideas.aha.io/ideas/APP-I-2702. Until that problem is fixed, I need an easy way to spot when Requirements and Stories have inadvertently drifted (i.e. Stories have been moved to anoth...
Guest almost 7 years ago in Jira 0 Future consideration

Set feature initial status on "Send to jira"

It would be nice to have a status set on the first send to jira. I have for example configured in jira integration page: Status "New" in Jira -> Status "In design" in Aha. So when I click the "Send to jira" button in the feature is should...
Szymon Lukaszczyk almost 7 years ago in Jira 4 Future consideration

Update JIRA with updated Aha Requirement definitions

When we update a requirement in Aha with a new or updated requirement definition, and there is already an existing JIRA link, the updated copy doesn't transfer over to the JIRA User Story, even when we select "Update JIRA" from the Actions menu.
Guest almost 7 years ago in Jira 1 Already exists

Feature History - Should show when a JIRA integration Link is Deleted

It would be valuable for the Features -> History audit trail to include information for when a JIRA integration link is deleted.
Matt Case about 7 years ago in Jira 0 Future consideration

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

Dedicated Integration User

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest about 7 years ago in Integrations / Jira 15 Future consideration

Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)

I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...
Guest about 7 years ago in Jira 3 Future consideration

Include JIRA records in linked records

We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
Guest about 7 years ago in Jira 2 Unlikely to implement

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