Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 264

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest over 7 years ago in Jira 3 Future consideration

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 JIRA Sen...
Guest over 7 years ago in Jira 5 Already exists

Support all types of JIRA text field formatting

The current JIRA integration doesn't support renderers other than the Wiki Style Renderer very well. Please add support for the other renderer types.
Guest almost 8 years ago in Jira 0 Unlikely to implement

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 8 years ago in Jira 0 Will not implement

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 8 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 almost 8 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 almost 8 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 resp...
Guest about 8 years ago in Jira 0 Unlikely to implement
195 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 8 years ago in Integrations / Jira 16 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 8 years ago in Jira 3 Unlikely to implement