From df5c80ab563785f4308c5fb376a6179f4e34b490 Mon Sep 17 00:00:00 2001 From: Andrea Alfonsi - INL Date: Thu, 18 Oct 2018 14:51:17 -0600 Subject: [PATCH] modified for the new NQ1 label called "task" (#812) --- .github/ISSUE_TEMPLATE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 0590afd883..284d8c2fee 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -18,7 +18,7 @@ Issue Description For Change Control Board: Issue Review ---------------- This review should occur before any development is performed as a response to this issue. -- [ ] 1. Is it tagged with a type: defect or improvement? +- [ ] 1. Is it tagged with a type: defect or task? - [ ] 2. Is it tagged with a priority: critical, normal or minor? - [ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements? - [ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. @@ -31,5 +31,5 @@ This review should occur when the issue is imminently going to be closed. - [ ] 1. If the issue is a defect, is the defect fixed? - [ ] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.) - [ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)? -- [ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? -- [ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided? +- [ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)? +- [ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?