Hello,
My team previously had an automation in place that when we marked a release version as "released" it would go through and mark all tickets in that version from a "Waiting for Release" status to "Released". This would then trigger other automation in our support system to let users know they were done.
All of the sudden in mid December, the release version button would no longer let us override the error telling us all tickets are not done. The release button is just inactive unless all the tickets are already marked as "released". Is there a way to work around this?
In the interim we have a new automation set up that when a version changes (so like we add the release date) it can transition all the tickets. But that seems more prone to error. Given the end goal is to easily transition all tickets from "Waiting for Release" to "Released" when a release goes live... any other suggestions?
We were trying to figure out how to use the new Release Approvers field in automations as well, thought maybe that could be the new Trigger, but couldn't seem to find an automation for that that would work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.