Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Hi,
Is it possible to have the PERT chart based on the Gantt chart created for a product ?
With that it will be more easy to work on the critical path.
Thank you.
Guest
almost 6 years ago
in Wanted
0
Future consideration
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Feature Email update notification to include link direct to Jira record
From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
Scott C
about 6 years ago
in Jira
0
Future consideration
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
about 4 years ago
in Jira
0
Future consideration
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...