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...
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
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
about 3 years ago
in Jira
1
Future consideration
We're working on an integration where we'd like to know the plan name for the product. For example we'd like to distinguish whether the plan is Ideas Advanced or Ideas Essentials. On the similar lines we'd also like to know for Roadmaps the plan n...
Guest
over 3 years ago
in Wanted
1
Future consideration
Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
over 3 years ago
in Jira
0
Future consideration
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe
over 3 years ago
in Jira
0
Future consideration
Allow Integration variable on Create Record layout
Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
This would allow the project management team to review and manage the project in AHA! and collaborate with Global teams on MS TEAMS by integrating the tasks.
Shane SWINEHART
over 3 years ago
in Integrations / To-dos
0
Future consideration