RELATED IDEAS
Option to sync fields to Rally upon creation only
When creating a record in Rally there are certain items that should be populated upon creation but not synced with subsequent updates.
For example, currently when creating or updating a record in Rally, Portfolio items are ordered based on their corresponding rank in Aha! which is determined by their sort order in the Features -> Board view. This is done by using the rankAbove/rankBelow parameter in Rally.
Changes to the rank in Rally are not reflected back into Aha! The problem that is introduced is that Engineering will sometimes need to change the order based on feature synergies or other considerations. However, if a feature is updated in Aha! and re-synced with Rally, it ends up resorting the Features in Rally back to the same original ranked order, undoing Engineering's changes.
If changes to the rank in Aha! were not sent to Rally this would resolve the issue.
-
ADMIN RESPONSEDec 18, 2017
We have launched an enhanced Rally integration. This integration will allow you to define sync directions on a field-by-field basis, including an option to only set once upon creation, along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Rally)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from Rally to make getting started in Aha! easy
Check out the blog post for more details.
