> Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh?
I don't think I've seen that reported before and we have been working through some interesting to reproduce issues in recent milestones.
Would you mind opening an issue for this? Feel free to tag me (same name).
I don't think I've seen that reported before and we have been working through some interesting to reproduce issues in recent milestones.
Would you mind opening an issue for this? Feel free to tag me (same name).