chore: revamp GH issues crossroad and templates#32454
chore: revamp GH issues crossroad and templates#32454Hotell merged 5 commits intomicrosoft:masterfrom
Conversation
📊 Bundle size report✅ No changes found |
b49c838 to
8f7585c
Compare
AtishayMsft
left a comment
There was a problem hiding this comment.
Thanks for a charting specific bug template Martin.
Didn't we agree to remove these? |
that was part of proposal ( optional ), we can remove as a follow-up |
|
I'd like to add a small suggestion regarding the organization of our bug report templates. For better readability, perhaps we could arrange the sections in this order:
instead of:
|
Adding summary would make actual behaviour/expected behaviour kind ambiguos. The intent here is to have things focused. We had "summary" before which contained "actual/expected" chapter which wasn't providing much clarity into what is actually needed from the reporter. 
Actual/Expected <-> Steps to Reproduce Initially I wanted to do it like this, I took data from various popular OSS repos and there is no clear pattern, some use it like in this PR, some like you suggest. One "against" having "steps to repro first" is the flow of person triaging. It doesn't make much sense to read Steps first when you don't know what those steps should demonstrate For now I suggest to keep it as is, but ofc happy to tweak things as we go. |
Co-authored-by: Oleksandr Fediashov <alexander.mcgarret@gmail.com>
bc98618 to
ac605e3
Compare
Previous Behavior
Issues crossroads UI:
New Behavior
Issues crossroads UI:
Bug reports changes highlights:
Library version fields
Before:
Not Present
After:
Improved Environment reporting
Before:
After:
Severity
Before:
After:
Reproduction
Before:
After:
Splitting Description in 2
Before:
After:
Related Issue(s)