Your release notes state:
The bi-directional integration includes two-way workflows for the following:
Comment - The third bullet is confusing since this is 1-way, not bi-directional. Our implementation team missed this fine point and trained everyone incorrectly. You should update your release notes.
Feature request - Make this a 2-way integration so that we do not lose the Status during the interim between when it is first sent to Rally and when someone updates the State field in Rally.
Why?/ Business Justification:
Product Manager maintains Status in Aha as the feature moves from Under Consideration to Defining to Ready for Engineering Review. Then, they Send to Rally. But since Rally does not receive this field, the entry becomes "No Entry". Then, as changes are made in Rally to fields that have 2-way integration (eg. description field), then it overwrites the Status in Aha the next time there is an update from Rally. Until someone on the Rally side changes the State in Rally, it will say "No Entry" on the Aha side, confusing everyone who has been monitoring this feature as it moves from Under Consideration to Defining, etc. This should be a 2-way integration or at the very least, the first Send to Rally should accept the Aha Status for its initial entry.
|Release time frame|
We have launched an enhanced Rally integration. This integration will allow you to create a 2-way state/status mapping, along with several other new capabilities including the ability to: