Merge pull request #498 from ut-issl/feature/fix-templates

Update PR and issue templates

.github/ISSUE_TEMPLATE/action_item.md

@@ -1,26 +1,25 @@
 ---
 name: Action Item
-about: For Action Item management
+about: Create an action item
 title: ''
 labels: ''
 assignees: ''
 
 ---
 
-## Overview
-Write briefly.
-
 ## Details
-Write in detail.
+Provide a detailed description of the issue.
 
-## Conditions for close
-When xxx is complete.
+## Closing conditions
+Provide the conditions that must be met for the issue to be closed.
 
-## Supplement
-Write additional comments if you need.
+## Supplementary information
+Provide any supplementary information.
 
 ## Note
-- If there are related Projects, tie them together.
-- Set `priority` label if possible.
-- Assignees should be set if possible.
-- Write a conclusion when closing the issue.
+- Provide a conclusion before closing the issue.
+<!--
+- Link the issue to any related projects if applicable.
+- Assign the appropriate member(s) to this pull request as `Assignees`.
+- Apply the `priority` label.
+-->

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,36 +2,35 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: ''
+labels: ['bug']
 assignees: ''
 
 ---
 
-## Overview
-Write briefly.
-
 ## Details
 ### Description
-What kind of bug?
+Describe the bug in detail.
 
 ### Conditions of occurrence
-The environment in which the bug occurs, the condition, parameters, etc.
+Describe the environment, conditions, parameters, etc. under which the bug occurred.
 
-###  Additional information
-files, link, etc, if any.
+### Additional information
+Provide any relevant files, links, etc. if available.
 
-## Task
+## Tasks
 - [ ] Fix xxx
 - [ ] Do yyy
 
-## Scope of influence
-eg. All tools are not working.
+## Impact
+Describe the scope of the bug's influence, e.g., `All tools are not working.`
 
-## Supplement
-Write additional comments if you need.
+## Supplementary notes
+Provide any extra notes if necessary.
 
-## Note
-- If there are related Projects, tie them together.
-- Set `priority` label if possible.
-- Assignees should be set if possible.
-- Write a conclusion when closing the issue.
+## Notes
+- Provide a conclusion before closing the issue.
+<!--
+- Link the issue to any related projects if applicable.
+- Assign the appropriate member(s) to this pull request as `Assignees`.
+- Apply the `priority` label.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +1,22 @@
-## Overview
-Write briefly.
+## Related issues
+Mention any issues that this pull request is related (e.g., #1). Consider using the `development` field if you want to close the issue automatically when this pull request is merged.
 
-## Issue
-- Related issues
+## Description
+Provide a detailed description of this pull request.
 
-## Details
-Write in detail.
+## Test results
+Provide the test results and a link to the detailed results log.
 
-##  Validation results
-Link to tests or validation results.
+## Impact
+Describe the scope of influence of the changes, e.g., `The behavior of feature ** changes.`
 
-## Scope of influence
-eg. The behavior of XX will be change.
-
-## Supplement
-Write additional comments if you need.
+## Supplementary information
+Provide any supplementary information.
 
+<!--
 ## Note
-- If there are related Projects, tie them together.
-- Assignees should be set if possible.
-- Reviewers should be set if possible.
-- Set `priority` label if possible.
+- No need to select `Reviewers` because it is automatically assigned.
+- Assign the appropriate member(s) to this pull request as `Assignees`.
+- Apply the `priority` label.
+- Link the issue to any related projects if applicable.
+-->