Luke Heath

Thanks, since this is estimated I'm moving straight to the release board. I know the inconsistency here has been confusing and resulted in some bugs. The important thing with a...

@mostlikelee I see this has been in estimated for 2 months just wanted to see if this is still a priority.

@mostlikelee Let's push this to next sprint. We want to focus on stability in 4.69.0 vs optimization (that may cause instability).

@marko-lisica Sorry, accidental add to drafting. Removed.

@noahtalerman Please @ mention the associated QA engineer and EM and assign the issue to them to make sure the bug doesn't fall off the radar.

@mostlikelee Please triage. Looks like there is a spike on drafting for this that could come in first as a timebox item.

Determining the root cause of the bug is included in the bug estimate. Moving back to ready to estimate.

@ddribeiro You got it - upgraded to P2. @sharon-fdm Please prioritize accordingly. Thanks!

Wow, this is a cool bug for QA Wolf to report outside of our UI! @noahtalerman Agreed we should prioritize as a P2, but I don't think it's a Fleet...

@jmwatts Thanks for the thorough testing! @mostlikelee Yep, since it needs engineering time I'm moving over to orchestration. @sharon-fdm Would you please deprioritize a lower priority issue to make room...