Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest
about 10 years ago
in Pivotal Tracker
2
Will not implement
We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
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...
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...
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
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
As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar
about 1 year ago
in Jira
0
Future consideration