Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match
If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Import from Jira: Ability to use more than one issue type for requirements
Merged
Import from Jira: Ability to use more than one issue type for requirements would be useful because we often have Jira Epics mapped to Aha! Features and those Epics have many different types of requirements that we would like to show dependencies i...
Our POs need to update user story summaries separately in Aha! and Confluence. If we had the ability to embed Confluence page info in Aha! and update the info from Aha! (push updates to Confluence) it would streamline information management. We us...
Kathleen Singleton
about 2 years ago
in Integrations
0
Shipped
1
MERGED
Link related items (i.e. dependencies) in VSTS integrations
Merged
Dependencies (and other relationships) between Features, Epics are important in VSTS for developer info. As far as I can see, 'related items' integration exists for JIRA but not VSTS?