In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
Guest
over 7 years ago
in Wanted
8
Future consideration
The ability to review previously ignored integration candidates and undo the ignore
What is the challenge? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...
Stephanie Lechner
almost 2 years ago
in Jira
4
Future consideration
Support OAuth for Jira integration instead of API token authentication
(Created using Elle!)Summary Enable OAuth-based authentication for the Jira integration so teams can connect Aha! to Jira without relying on long-lived API tokens or personal access tokens. Problem Token-based authentication creates administrative...
Joseph Gehling
4 months ago
in Integrations
0
Future consideration
Sync Aha! Releases to Azure DevOps iterations at all levels
What is the challenge?
People working in both Aha! and Azure DevOps (ADO) modify the "Iteration" field found on user stories and bugs in ADO.
As releases solidify, some work items may no longer be planned to be included, and new ones may have ...
I know that Aha includes the ability to attach documents at the Product Level. However, at my company, we want to maintain Policies & Procedures, but take advantage of the version control available in SharePoint. We want to link or integrate a...
Karen Wittenberg
over 9 years ago
in Integrations / Notes
7
Future consideration
Add ability to restrict auto import of parent record with ADO
What is the challenge?
When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha!
What is the impact?
Difficulty in ...
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
Russell Roach
almost 6 years ago
in Jira
3
Future consideration