Flow to mark a release plan as completed

[maririos]

Create a cloud flow that given a release plan ID, change the state of the release plan to Finished/completed and add tag auto-closed.
More context in issue #8290

[maririos]

New flow created under the name Manually complete a release plan
Test in dev: https://dev.azure.com/azure-sdk/Release/_workitems/edit/18827/

[ladonnaq]

Create a cloud flow that given a release plan ID, change the state of the release plan to Finished/completed and add tag auto-closed. More context in issue #8290
I created a query that identifies all of the release plans tagged auto-complete or auto-abandon. Do you want to use the query in the cloud flow and then remove the tags after complete and add tag auto-closed?

[maririos]

I created a query that identifies all of the release plans tagged auto-complete or auto-abandon. Do you want to use the query in the cloud flow and then remove the tags after complete and add tag auto-closed?

If you are manually adding those tags, then i will prefer for you to keep filling an issue with the release plan numbers and we will run the respective flows

[ladonnaq]

[like] LaDonna Quinn reacted to your message:

…

________________________________ From: Mariana Rios Flores ***@***.***> Sent: Friday, August 23, 2024 7:43:00 PM To: Azure/azure-sdk-tools ***@***.***> Cc: Comment ***@***.***> Subject: Re: [Azure/azure-sdk-tools] Flow to mark a release plan as completed (Issue #8872) I created a query that identifies all of the release plans tagged auto-complete or auto-abandon. Do you want to use the query in the cloud flow and then remove the tags after complete and add tag auto-closed? If you are manually adding those tags, then i will prefer for you to keep filling an issue with the release plan numbers and we will run the respective flows — Reply to this email directly, view it on GitHub<#8872 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQEFYOUIUEYV4FO3B62H34LZS6GEJBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDGNJUGA3TINBSGOSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRUGI4DKMBUGU2DOMNENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTCNZQGU4TEMJYG2BKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2DQMRQGI2TCOBWQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRSGM2TIMBXGQ2DEM4CUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNBSHA2TANBVGQ3TDJ3UOJUWOZ3FOKTGG4TFMF2GK>. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.