When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...

When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...

What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...

Looking to see what capabilities can be enabled to help us integrate initiative and feature level data with Broadcom Clarity PPM for our Digital automated timecard process.

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually

What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...

When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!

What is the challenge? In Salesforce if I merge an account into another account any ideas that were linked on the source account are transferred over to the target account. On the Aha! side, the link in the proxy vote to the account still points b...

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...