Ability to map an initiatives "assigned to" field with a user field within an integration
When mapping an initiative to a record in a development tool, it would be helpful to have the ability to map the "assigned to" field from Aha! to a user field. This would be helpful when initiatives are mapped to EPICs so the assigned user can syn...
Shawn Zenz
over 5 years ago
in Integrations
1
Future consideration
In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...
Mat Buehler
over 2 years ago
in Jira
1
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
10 months ago
in Integrations
0
Future consideration
If a comment is deleted in Jira, please delete that comment in Aha! also
Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes
over 7 years ago
in Jira
1
Will not implement
Support an integration with BetterWorks to sync goals, success metrics and initiatives
As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com)
Note: both Be...
Guest
about 9 years ago
in Integrations
0
Unlikely to implement
Notify users on Slack when they are tagged in Aha! through slack integration
Right now - when tagging someone in Aha! it links the user on Aha! to the comment e.g. Comment by XXX@YYY (link to user in Aha!) .... But it is useless to have it that way - it would be much nicer if the tagging on the comment in Aha! corresponded...
Nir Soffer
about 5 years ago
in Slack
2
Future consideration
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
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 10 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...
Guest
over 1 year ago
in Jira
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