In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
Max Cascone
over 6 years ago
in Jira
1
Future consideration
We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
Integrations 2.0: Allow Master Feature relationship for Requirements
I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
Danny Archer
over 6 years ago
in Integrations
0
Future consideration
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Custom Record Type, Made Up Entirely Of Custom Fields
We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
Allow fields from linked records to be mapped to integration fields
It would be useful to be able to map additional data from linked records when setting up integrations with my development system.
For example, when configuring the feature field mapping I may want to pass over the initiative a feature is linked to...
Todd Meyer
over 6 years ago
in Integrations
0
Future consideration
As a Rally Admin, this wording can be be quite confusing. I've had to explain it several times to users. Suggestion: Instead of Excluding, "Included Child Updates" - box is automatically checked, so users can uncheck if excluding those updates.
Victoria Morrella
about 3 years ago
in Rally
0
Future consideration
When sending a Release to Pivotal Tracker, items are added to the backlog in reverse order
Items are prioritized in Aha's release area by the Product Manager. When sending the release to Pivotal Tracker, the Stories that appear in PT are in reverse order, meaning the engineering team must spend time comparing lists to fix the order.
I ...
Guest
about 8 years ago
in Pivotal Tracker
1
Future consideration
Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status
We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
Guest
over 3 years ago
in Jira
1
Future consideration
For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields.
There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed ...
Tim McCaskill
almost 5 years ago
in Integrations
1
Future consideration