Scheduled releases - changing release date - without need to workflow
considered for backlog
M
Melanie Williams
We need a way to be able to change a release date on an asset, after you've set it - without the need to workflow it again.
Example - you schedule the release of an asset - say set it to 01/05, however say there is an issue with the project I am working on, and I either need to release the asset sooner or push out the release date. I cannot change the date without work flowing it?
In general Work flowing items for every change is a key friction point.
- It takes resource of min two people (as needs a final approver - we need to avoid people approving their own assets - to give us robust controls)
- And can not therefore be a one and done action (needs people to go back and forth to action the update and any next steps).
L
Laura Cara Dominguez
To add a note to this; at the moment we can start an edit workflow but we cannot withdraw the existing Scheduled asset - it would be very helpful to have this option as well.
We have had an example of an user who needed to change the release date of a Scheduled asset based on a change of plans. They don't have the new date confirmed so cannot release the edits, but also cannot withdraw the Scheduled one and has to wait for it to be released to do it.
Bram Timmers
updated the status to
considered for backlog
Bram Timmers
Later this year, we're planning to introduce a significant improvement to the ease with which asset info can be edited, along with the ability to leverage multiple (context aware) approval workflows. Situations like the one you describe (where a release date is adjusted, while the asset is 'scheduled'), or when they contain changes that are low-risk (by the viewpoint of the organisation owning the workspace, that is), could then be exempted from having to go through another approval workflow