New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration
There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin
over 3 years ago
in Jira
0
Future consideration
Map detailed estimates by initiative in Jira integration
What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus
about 1 year ago
in Jira
0
Future consideration
As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar
over 2 years ago
in Jira
0
Future consideration
We have been testing our Aha/Redmine integration and ran into an issue with a workflow:
Existing redmine target version is named "2.6.0" Existing Aha release is named "2.6.0" When I copy an Aha feature to redmine, I get an error that says "name al...
Matt Case
over 10 years ago
in Integrations
2
Unlikely to implement
Our customer success team uses Help Scout as their main support tool to assist our customers. It'd be nice if they could just take the feedback given by customers in their Help Scout ticket and send it directly into Aha! as an idea.
Jacob Papka
over 3 years ago
in Integrations
0
Future consideration
Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong
over 3 years ago
in Jira
0
Future consideration
Copy integration mappings for records at the same hierarchy level
When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush
over 2 years ago
in Jira
0
Future consideration
Allow two-way integration for picklist fields in Azure DevOps when using the XML process model
This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...