What is the challenge? |
Some advanced use-cases (such as tracking the history of a release assignment of a feature) are not possible today. |
What is the impact? |
This prevents users from tracking slipped work for work which has been re-assigned many times. |
Describe your idea |
Creating an automation action which would allow creating a new custom table record would solve this and many other use-cases. For example, creating a "ReleaseAssignment" one-to-many custom field, having a date and a release record, and then creating a record every time that a feature's release_id changes, would allow tracking and reporting on all rescheduled release assignments |