Skip to content

Update issue templates with new supported values#8718

Merged
anmenaga merged 17 commits intoPowerShell:masterfrom
RDIL:patch-2
Jan 25, 2019
Merged

Update issue templates with new supported values#8718
anmenaga merged 17 commits intoPowerShell:masterfrom
RDIL:patch-2

Conversation

@RDIL
Copy link
Copy Markdown
Contributor

@RDIL RDIL commented Jan 23, 2019

PR Summary

GitHub now supports new values on issue templates, so here they are.

PR Context

PR Checklist

TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
@RDIL
Copy link
Copy Markdown
Contributor Author

RDIL commented Jan 23, 2019

Suggestions accepted.

TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
TravisEz13
TravisEz13 reviewed Jan 23, 2019
View reviewed changes
@anmenaga anmenaga merged commit 719b808 into PowerShell:master Jan 25, 2019
@RDIL RDIL deleted the patch-2 branch January 25, 2019 20:15
@iSazonov
Copy link
Copy Markdown
Collaborator

iSazonov commented Jan 29, 2019 •
edited
Loading

Now we have many issues with bug label what doesn't look right :-( I think the label should be assigned only for confirmed bugs.

Also [DOCS] and others in title look superfluous.

@TravisEz13 @SteveL-MSFT Thoughts?

@SteveL-MSFT
Copy link
Copy Markdown
Member

SteveL-MSFT commented Jan 29, 2019

@iSazonov I agree, the original intent of the Issue - Bug label is when it's a identified bug, not a possible bug. Perhaps we should add a Issue - Needs Triage label that gets put automatically, then after someone has taken a look, it can be bug, discussion, etc...?

@iSazonov
Copy link
Copy Markdown
Collaborator

iSazonov commented Jan 30, 2019

We could reuse "discussion" label - in any case,sooner or later, issues with "discussion" should be triaged to bug, enhancement , up-to-grabs or closed by-design or wont-fix.
Also we could don't initially label issues with bug template at all and make this manually after first review or after initial discussion.

@SteveL-MSFT
Copy link
Copy Markdown
Member

SteveL-MSFT commented Jan 30, 2019

@iSazonov that might work for now and we can revisit later anyways, do you want to submit a PR?

@iSazonov
Copy link
Copy Markdown
Collaborator

iSazonov commented Jan 30, 2019

Done #8792

@TravisEz13 TravisEz13 added CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log and removed CL-Untagged labels Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@TravisEz13 TravisEz13 TravisEz13 approved these changes

@joeyaiello joeyaiello Awaiting requested review from joeyaiello

@SteveL-MSFT SteveL-MSFT Awaiting requested review from SteveL-MSFT

Assignees

@anmenaga anmenaga

Labels

CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@RDIL @iSazonov @SteveL-MSFT @TravisEz13 @anmenaga