Problem Description:
For programs where XLR templates are changed by people multiple times in a day, we need an approval process for template changes. The current 2-way BitBucket control in XLR is rudimentary and Manual, also it has quite a few bugs. Hence a trigger for file changes will be helpful. Based on this trigger, we can start an approval process.
Feature:
A trigger for XLR template changes. XLR already has activity log which tracks when individual files change so creating a trigger is something that can be worked on.
The release configured for the trigger activated when any file under that folder or any subfolders changes. The trigger variable contains the file names of the files changed, along with the full path.
Somebody submits a change -> then there is a mechanism that allows for review and perhaps testing prior to implementation of the changes in the main template. This should be an automated process, whereas once the change is submitted - a review process kicks off without further human effort. The review itself will involve people and testing.
by: Devon G. | about a month ago | API & CLI tools
Comments
Thanks for the idea. To better understand the request and align with the needs, could you clarify a few points below:
1. What should qualify as a "template change" that requires triggering the approval process?
2. Could you walk us through how you imagine the approval process working once a change is detected?
* For example, do you envision this triggering a specific approval template inside Release?
3. Once a change is approved, what should happen next?
* Should the main template be updated automatically?
* Or do you expect a manual step to publish or promote the changes?