Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest
about 6 years ago
in Jira
0
Future consideration
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
Jonathon Leeke
about 9 years ago
in Integrations
6
Already exists
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Allow project access token to be used instead of personal token for GitLab integration
Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest
9 months ago
in Integrations
0
Future consideration
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck
about 6 years ago
in Pivotal Tracker
1
Future consideration
Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)
Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest
9 months ago
in Integrations
0
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi
over 5 years ago
in Jira
2
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
over 5 years ago
in Jira
0
Future consideration