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
over 1 year ago
in JiraFuture 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 ...
Add the sprint rank (order) of a PBI to the integrations so Aha has the order of PBIs in a Sprint (Iteration)
What is the challenge?
I cannot create a report in Aha where I can sort the requirements (PBIs) by their ADO rank.
What is the impact?
Limits my ability to create recurring reporting informing stakeholders of sprint priorities and limits A...
Add Integration updates and errors to record history
What is the challenge?
Integration updates and errors primarily appear within the integration logs. These are separate to the records, meaning it can be hard to relate them back to the relevant record.
What is the impact?
It can be difficu...
Chris Quigley
about 2 months ago
in IntegrationsUnlikely to implement
Extend webhook triggers so they can fire on additional field updates
What is the challenge?
Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...
Justin Woods
5 months ago
in IntegrationsFuture consideration
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
almost 7 years ago
in WantedFuture consideration
What is the challenge? When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool...
Jeanette Resnikoff
about 1 year ago
in JiraFuture consideration