Allow for Lookup Fields to be mapped in SFDC integration
Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Julie Joyce
over 1 year ago
in Salesforce
0
Future consideration
More complete field mapping between Aha! and FogBugz
Both products are feature rich and have many alignments which would be great to keep in sync.
Aha! Feature Type - FogBugz Case Category
FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest
over 10 years ago
in Integrations
4
Will not implement
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...
Guest
over 1 year ago
in Jira
0
Future consideration
Option to ignore changes to Items that AHA does not know about.
We have joined Azure Dev Ops to Aha via the integrations.
In fact there will by 7+ Integrations due to the size of the portfolio.
We have restricted the webhooks so that:
New / Updates to (Release / Epic Work Item types) are pushed to AHA from ...
Guest
about 6 years ago
in Integrations
0
Future consideration
Update blank Jira fields on import to Aha! even if they are set up as a two-way sync
Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
Diane Metzger
11 months ago
in Integrations
0
Future consideration
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
Nico Arias-Gonzalez
over 1 year ago
in Integrations / Jira
0
Future consideration
Provide the ability to set default filters on the integration updates Feature.
I have Product Owner access in multiple products to assist with managing the layouts and set up of the products in Aha, but I do not want to worry about accidentally ...
Guest
almost 8 years ago
in Integrations
0
Future consideration
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes me...
Michael Clinton
over 9 years ago
in Jira
1
Future consideration
As a workspace admin viewing the Integration Messages Log - I'd love to be able to click these buttons at the top of the log to filter just to "Errors" in red, "warnings" in yellow or "info" in blue - currently most updates are "info" and importan...
Karla Johnson
over 3 years ago
in Rally
0
Future consideration
Provide additional filter/criteria while setting up the Rally integration
Currently, Rally integration is setup at a Workspace/project level. It would help immensely to be able to add additional criteria, like Tags = XXX or Status = 'YYY'. This will help to filter out records that would show up for import. This will hel...
Jyothirmayi Talaparthy
about 5 years ago
in Rally
0
Future consideration