Integrations

Showing 945 of 9086

Integrate existing FogBugz cases into Aha! as features (similar to JIRA 2way integration)

This will allow teams that use FogBugz to onboard to Aha! easier, without having to orphan FogBugz cases already entered that cannot speak back to Aha! through the current FogBugz integration.

amy kennedy almost 9 years ago in Integrations 2 Unlikely to implement

1 VOTE

Conditional Notifications for Activities & To-dos

Aha! needs more robust notification functionality—particularly, conditional formatting. We use Aha! to manage GTM activities associated with product launches. I would like to use Aha! to send automated reminders/alerts to activity & to-do assi...

Blake Birdwell over 1 year ago in Comments / Notifications / Slack 0 Future consideration

4 VOTE

Be able to bulk update only rank or a single field within JIRA integration

Normally our product managers works on Initiatives in Aha! by editing/ranking them. Those field changes and ranking will sync to Jira backlog for architect team to work on follow priority of Initiatives. When a rank is changed for a record in Aha!...

Guest about 6 years ago in Integrations 0 Future consideration

4 VOTE

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). U...

Guest about 6 years ago in Jira 0 Future consideration

1 VOTE

Confluence link to List Report is not updating properly

I created a List Report in Aha and output to a webpage which I then embedded in a Confluence page using the Confluence Aha App. I made a change in Aha to the title of a Feature and the change was not reflected in the Confluence page embedded webpa...

Debra T over 1 year ago in Integrations 1 Already exists

4 VOTE

Link Aha! feature to an already existing pivotal story

It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.

Guest about 6 years ago in Pivotal Tracker 1 Will not implement

4 VOTE

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 about 6 years ago in Jira 1 Already exists

5 VOTE

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 over 7 years ago in Jira 0 Future consideration

6 VOTE

When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal

Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint. When this happens, ...

Jason Novek over 9 years ago in Pivotal Tracker 0 Will not implement

1 VOTE

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...

Guest over 1 year ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY