Support large volumes of repos in GitHub integration
My company has been migrating from GHE to GitHub.com, and the default repo permission is set to "internal". This is causing individual users to have access to over 15k repos. In Aha, this large number of repos is preventing users from being able t...
David I.
over 2 years ago
in GitHub
0
Future consideration
Tags should propagate bidirectionally into Pivotal Tracker
Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Jason Novek
about 10 years ago
in Pivotal Tracker
2
Will not implement
What is the challenge?
As a system administrator, I need to have a quick and comprehensive view of all the different integrations to help me troubleshoot and support the environment
What is the impact?
It takes time and effort to manually ...
Guest
6 months ago
in Integrations
0
Future consideration
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...
Guest
about 10 years ago
in Jira
8
Unlikely to implement
Allow Aha! user name to populate DevOps board user
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...
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest
over 3 years ago
in Jira
1
Future consideration
Enable Roll-up Initiative link in the standard Azure DevOps Services integration
What is the challenge?
Unable to integrate multi-layered strategic initiatives from Aha to ADO
What is the impact?
Manual updates to keep information in sync, prone to errors. Question whether we will continue to utilize Aha or work direct...
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 ...
Guest
almost 7 years ago
in Jira
2
Future consideration
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 8 years ago
in Jira
3
Future consideration
Rally integration - Create and update dependency relationships between features as part of two-way integration
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!
Matt Case
over 9 years ago
in Dependencies / Rally
2
Future consideration