Ability to link features/requirements to existing VSO work items
Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful
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...
Our Marketing team uses HubSpot to schedule social media posts, for example. It would be awesome to plug into their tool so we can push marketing tasks with relative dates, and they can relay when those are ready and completed. It's unlikely marke...
Guest
about 10 years ago
in Integrations
1
Shipped
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...
Allow customization of on-prem Jira link displayed in Feature details so that link actually works
High-level:
The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement req...
We use Master Releases when we have multiple products shipping together. I need the Master Release name to appear in Jira for reporting.
I'm flexible as to how this can be done. Maybe a way to create a custom field on the feature level that auto-p...
Avigail Ehrenhaus
over 10 years ago
in Jira
0
Shipped
VSO does not have a good handle on representing releases. Can't really use the iteration mechanism, if your team is working on overlapping releases. Currently I'm using a highest level Feature in VSO to represent a release (or the Backlog) and the...
An Aha feature pushed to Rally creates the Feature/User Story in Rally as well as the Release information. An Aha feature in the Parking Lot (not tied to a specific release) will still be created in Rally, but there is an error message with the re...
Need to "Link with existing issue in JIRA" at requirement level
We have JIRA and Aha today and the tools are integrated as follows:
Aha feature - JIRA Epic
Aha requirement - JIRA story
NA - JIRA sub-task
For some reasons, I had to delete the integration with JIRA for a specific product line from Aha an...