Support bulk remove of JIRA links from "Features List"
Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest
about 8 years ago
in Jira
1
Future consideration
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest
almost 5 years ago
in Jira
0
Future consideration
Who would benefit? Anyone who wants to send an audit record of full item state on change What impact would it make? Default should remain only changed columns to avoid making this a breaking change. Full state will obviously generate a larger payl...
Sandy Teenan
7 months ago
in Integrations
0
Future consideration
Ability to set Aha field to a constant value as part of integration field mappings
My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
Need to support the Jira code markup option.
If the developer enters sample code as part of the description in Jira, the description gets updated in Aha!
However the code markup is translated into very large tables in Aha!
At some point, Aha! u...
Guest
over 8 years ago
in Jira
2
Future consideration
Within an ideas portal, using the search ability will return ideas that match on all of the words. When searching from the Salesforce integration, the results are different since they are matched on any of the words. Utilizing the same search meth...
Need to functionality to include Custom Table fields in the integration mapping. We created a new table for Aha Roadmaps for Program Increments. The table is linked to both Epics and Features, to simplify the reports (same value for both). The cha...
Edgar Holguin
about 1 year ago
in Jira
0
Future consideration
Who would benefit? Users of both Aha and those who are not direct users of Aha on a daily basis but who relay on outputs from the platform. What impact would it have? It would simply data sharing and through Microsoft products such as Teams, Word,...
Guest
7 months ago
in Integrations
0
Future consideration
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...