Integrate Aha Program Increment (PI) custom field with Rally Release field
Today in Rally, following an orthodox SAFe Portfolio model, we organize our work based on Product Increment (PI) intervals that include four(4) two week sprints and on two week sprint for Innovation and planning. Every ten weeks we hold another PI...
Guest
about 6 years ago
in Rally
0
Future consideration
Ability to view the specific development integration that an object is using
There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system.
This would help to identify when integrations are being 'cut over' in order to tra...
Guest
about 6 years ago
in Integrations
1
Future consideration
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet
over 5 years ago
in Jira
1
Future consideration
What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
Matt L
8 months ago
in Jira
0
Future consideration
When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA
Hi All,
We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
Guest
over 8 years ago
in Ideas / Jira
4
Unlikely to implement
Function as a hub to push data from JIRA to DevOps
We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest
almost 2 years ago
in Jira
0
Future consideration