resolve audit findings for problem resolution

Add example using the new issue template

Resolves: #86

Author: masc2023

process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst

@@ -30,8 +30,13 @@ The detailed implementation of the Problem Resolution for the project shall be d
 Templates
 ---------
 
-To create problem reports, the project shall provide the following template: :need:`[[title]]<gd_temp__problem__template>`.
-An example template for the issue trackings system GitHub can be found here: (to be updated later)
+To create problem reports, the project shall provide the content of the following template
+in project's selected Issue Tracking System: :need:`[[title]]<gd_temp__problem__template>`.
+
+.. note::
+  An example template for the Issue Tracking System in GitHub (`GitHub Issues <https://github.com/features/issues>`_)
+  can be found here:
+  `Issue Template Bugfix <https://github.com/eclipse-score/process_description/blob/main/.github/ISSUE_TEMPLATE/1-bugfix.yml>`_
 
 Attributes
 ----------
@@ -85,18 +90,51 @@ This section describes in detail which steps need to be performed for a Problem
 Create Problem Report
 ---------------------
 
-:need:`[[title]] <rl__contributor>` (as author) creates the Problem Report in the defined Issue
-Tracking System based on the provided template.
-It is expected, that the UID will be provided by the Issue Tracking System.
+:need:`[[title]] <rl__contributor>` (as author, submitter, reporter) creates the Problem
+Report in the defined Issue Tracking System of the project based on the content of the
+provided template:
+:need:`[[title]]<gd_temp__problem__template>`.
+
+It is expected that the select Issue Tracking system supports template definition. Best
+practice is to define a template with the required content, so that it can be copied
+from the different users.
+
+.. note::
+  For the Issue Tracking System in GitHub, there is a template created, which can be
+  be found here:
+  `Issue Template Bugfix <https://github.com/eclipse-score/process_description/blob/main/.github/ISSUE_TEMPLATE/1-bugfix.yml>`_
+
+.. note::
+  A Problem Report Example based on that template is here:
+  `Example Problem Report <https://github.com/eclipse-score/process_description/issues/124>`_
+
+It is expected, that the UID will be provided automatically by the Issue Tracking System.
+
+It is expected, that the status of the problem report is set to "open" automatically.
+As long as the content is updated, the status of the Problem is kept "open".
+
+It is expected, that the problem submitter will be set automatically by the Issue
+Tracking System.
 
 The title of the Problem Report should reflect the topic accordingly.
 
 The description should reflect the problem root cause and impact in detail.
 
-Copy therefore the :need:`Problem Template <gd_temp__problem__template>` into the created Problem
-Report (Issue Tracking System).
-
-Set the status of the Problem to "open", when ready to review and analyze set to "in review".
+.. note::
+  | For the Problem Report Example:
+  | * The UID is provided by the Issue Tracking System as: **#124**
+  | * The status is provided by the Issue Tracking System as: **Open**
+  | * The submitter is provided by the Issue Tracking System as: **masc2023**
+  | * The title contains the main root cause, missing safety/security attribute
+  | * The descriptions has a section for the root cause and impact
+  | * Further supporting information is added as the link to the official feature request template
+
+When ready to review and to analyze, the reporter sets the status to "in review" manually.
+
+.. note::
+  | For the Problem Report Example:
+  | * The "Process Development Community" dashboard is added and the status must be changed to **Todo**
+  | * The combination of **Open** and **Todo** defines the status **in review**
 
 .. _prm_analyze_problem_report:
 

process/process_areas/problem_resolution/guidance/problem_resolution_template.rst

@@ -22,31 +22,27 @@ Problem Report Template
    :status: draft
    :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP3, std_req__aspice_40__SUP-9-BP4,
 
-Will be reworked, after this PR with ISSUE_TEMPLATES is merged
-
 Problem status
 --------------
 [“open”, “in review”, “in implementation”, “closed”, “rejected”]
 
 If possible, use for problem status the properties of the selected Issue Tracking System.
-(Update here with example from GitHub, after this PR is merged)
 
 | (to be filled out during :need:`wf__problem__create_pr`)
 | (to be updated during :need:`wf__problem__analyze_pr`)
 | (to be updated during :need:`wf__problem__initiate_monitor_pr`)
+| (to be updated during :need:`wf__problem__close_pr`)
 
 Problem submitter
 -----------------
 [Who is the reporter of the problem?]
 
 If possible, use for problem submitter the properties of the selected Issue Tracking System
-(for implementation see here: to be update with Example later)
 
 (to be filled out during :need:`wf__problem__create_pr`)
 
 Problem description
 -------------------
-
 [What is the problem?]
 
 | Determine the cause of the problem, if possible.
@@ -61,7 +57,8 @@ Problem supporting information
 
 [How to reproduce the problem?]
 
-(to be filled out during :need:`wf__problem__create_pr`)
+| (to be filled out during :need:`wf__problem__create_pr`)
+| (to be updated during :need:`wf__problem__analyze_pr`)
 
 Problem analysis results
 ------------------------
@@ -81,9 +78,8 @@ Problem stakeholder
 Add affected feature, if possible
 
 If possible, use for problem stakeholder the properties of the selected Issue Tracking System
-(Update here with example from GitHub, after this PR is merged)
 
-(to be filled out during :need:`wf__problem__create_pr`)
+(to be updated during :need:`wf__problem__analyze_pr`)
 
 Problem category
 ----------------
@@ -97,7 +93,6 @@ Problem category
 Safety, Security: Additional qualifier to highlight, if safety or security is affected
 
 If possible, use for problem category the properties of the selected Issue Tracking System
-(Update here with example from GitHub, after this PR is merged)
 
 (to be filled out during :need:`wf__problem__create_pr`)
 
@@ -147,7 +142,6 @@ Problem expected closure date
 [Milestone when the problem should be resolved]
 
 If possible, use for problem closure date the properties of the selected Issue Tracking System
-(Update here with example from GitHub, after this PR is merged)
 
 (to be filled out during :need:`wf__problem__create_pr`)
 

process/process_areas/problem_resolution/problem_resolution_concept.rst

@@ -44,12 +44,24 @@ Stakeholders for the Problem Report
 
 #. :need:`Contributor <rl__contributor>`
 
-   * Contributes features and components to grow the project content
+   * In general contributes features and components to grow the project content
+   * Reports problems, analyze problems, implement problem resolutions
 
 #. :need:`Committer <rl__committer>`
 
-   * Verifies that the contribution fulfills the project policies
-   * Approves the contribution
+   * Verifies that the contribution including problem resolutions fulfills the project policies
+   * Approves all problem resolution activities besides problem closing
+   * Is responsible to initiate the the closure of the problem reported
+
+#. :need:`Technical Lead <rl__technical_lead>`, :need:`Module Lead <rl__module_lead>`
+
+   * Supports all problem resolution activities
+   * Approves the closing of the problem resolution
+
+#. :need:`Safety Manager <rl__safety_manager>`, :need:`Security Manager <rl__security_manager>`, :need:`Quality Manager <rl__quality_manager>`
+
+   * Supports all problem resolution activities
+
 
 Standard Requirements
 =====================
@@ -58,15 +70,7 @@ Also requirements of standards need to be taken into consideration:
 
 * ISO 26262
 * ASPICE
-* ISO SAE 21434
-
-Problem Report Categories
-*************************
-
-User: Problems relating to requirements, architecture, implementation, or code found by user of the platform.
-
-Bug: Problems found by contributor based on component, feature or platform integration tests including verification and quality assurance activities.
-
+* ISO/SAE 21434
 
 .. _prm_attributes: