@WG-prioritization/alerts issue #41078 has been requested for prioritization.
wow, people keep running into this
same issue I think
oh wait this is the original :laughing:
yeah P-medium seems fine - it's confusing, but there's a workaround
P-high, if it's tripping up newcomers it's probably hit fairly often.
Also to (indirectly) reduce people's workload on commenting on duplicate issues by fixing this.
Hmm, fair enough. It doesn't seem like it will be fixed any time soon but I guess that shouldn't affect the prioritization.
@Hameer Abbasi you make a good point. Although "worth" a medium, I'd vote to assign a
P-high and have the team briefly discuss it (I'll try summarizing the issue history in the agenda)
at the very least we have an evaluation about the effort to "fix" or "work around" to improve ergonomics
can we instead use I-nominate if you think it's 'worth' a medium?
I don't think we should change the priority just so it will be discussed at the weekly meeting
In my book there are two things that determine a bug's worth. Severity and frequency. This is a medium on the severity scale but fairly high on the frequency scale.
right, and if we mark it P-high for that reason that's fine with me, but it shouldn't be so it's brought up at the weekly meeting, we have
I-nominate for that
I agree with Joshua, issue nomination is a better tool to discuss (my bad that I sometimes forget about it :sweat_smile: )
I agree with
I-nominate P-medium too.
Issue #41078's prioritization request has been removed.
The issue wasnt discussed due to time constraints (I added it to the very last minute), so it will slip to next week