Skip to content

Commit 32daebb

Browse files
committed
add SCORE_ for the links to the SCORE Project Management Plan
1 parent bcaf2cb commit 32daebb

File tree

5 files changed

+10
-10
lines changed

5 files changed

+10
-10
lines changed

process/process_areas/documentation_management/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,5 +27,5 @@ Documentation Management
2727
documentation_workflow
2828
documentation_workproducts
2929

30-
.. needextend:: "process_areas/documentation_management" in docname
30+
.. needextend:: "process/documentation_management" in docname
3131
:+tags: doc_mgt

process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This document describes the general guidances for Problem Resolution based on th
2525
General Hints
2626
=============
2727

28-
The detailed implementation of the Problem Resolution for **S-CORE** is described in the :need:`[[title]]<doc__platform_problem_resolution_plan>`.
28+
The detailed implementation of the Problem Resolution for **S-CORE** is described in the :need:`[[title]]<SCORE_doc__platform_problem_resolution_plan>`.
2929

3030
Templates
3131
---------
@@ -54,7 +54,7 @@ Activities for Problem Resolution
5454

5555
This section describes in detail which steps need to be performed for a Problem resolution.
5656

57-
Refer to the :need:`Problem Resolution Plan <doc__platform_problem_resolution_plan>` for examples
57+
Refer to the :need:`Problem Resolution Plan <SCORE_doc__platform_problem_resolution_plan>` for examples
5858
how to create problem reports.
5959

6060
.. list-table:: Activities for Problem Resolution

process/process_areas/problem_resolution/guidance/problem_resolution_template.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Problem status
3131
[“open”, “in review”, “in implementation”, “closed”, “rejected”]
3232

3333
If possible, use for problem status the properties of the selected Issue Tracking System
34-
(for implementation see here :need:`doc__platform_problem_resolution_plan`)
34+
(for implementation see here :need:`SCORE_doc__platform_problem_resolution_plan`)
3535

3636
| (to be filled out during :need:`wf__problem__create_pr`)
3737
| (to be updated during :need:`wf__problem__analyse_pr`)
@@ -42,7 +42,7 @@ Problem submitter
4242
[Who is the reporter of the problem?]
4343

4444
If possible, use for problem submitter the properties of the selected Issue Tracking System
45-
(for implementation see here :need:`doc__platform_problem_resolution_plan`)
45+
(for implementation see here :need:`SCORE_doc__platform_problem_resolution_plan`)
4646

4747
(to be filled out during :need:`wf__problem__create_pr`)
4848

@@ -83,7 +83,7 @@ Problem stakeholder
8383
Add affected feature, if possible
8484

8585
If possible, use for problem stakeholder the properties of the selected Issue Tracking System
86-
(see implementation here :need:`doc__platform_problem_resolution_plan`)
86+
(see implementation here :need:`SCORE_doc__platform_problem_resolution_plan`)
8787

8888
(to be filled out during :need:`wf__problem__create_pr`)
8989

@@ -106,7 +106,7 @@ Bug:
106106
Safety, Security, Quality: Additional qualifier to highlight, if safety, security or quality is affected
107107

108108
If possible, use for problem category the properties of the selected Issue Tracking System
109-
(for implementation see here :need:`doc__platform_problem_resolution_plan`)
109+
(for implementation see here :need:`SCORE_doc__platform_problem_resolution_plan`)
110110

111111
(to be filled out during :need:`wf__problem__create_pr`)
112112

@@ -145,7 +145,7 @@ Problem expected closure date
145145
[Milestone when the problem should be resolved]
146146

147147
If possible, use for problem closure date the properties of the selected Issue Tracking System
148-
(for implementation see here :need:`doc__platform_problem_resolution_plan`)
148+
(for implementation see here :need:`SCORE_doc__platform_problem_resolution_plan`)
149149

150150
(to be filled out during :need:`wf__problem__create_pr`)
151151

process/process_areas/problem_resolution/problem_resolution_getstrt.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,5 +24,5 @@ In case you want to report a Problem to **S-CORE** consider to:
2424

2525
* Create your Problem Report according to :need:`wf__problem__create_pr`
2626
* Make familiar with the development and supporting process descriptions in :ref:`process_description`
27-
* Make familiar with the relevant sections of the :ref:`Platform Management Plan <pmp>`, here especially with :need:`Problem Resolution Plan <doc__platform_problem_resolution_plan>`
27+
* Make familiar with the relevant sections of the :ref:`Platform Management Plan <pmp>`, here especially with :need:`Problem Resolution Plan <SCORE_doc__platform_problem_resolution_plan>`
2828
* In case of any questions, contact the :need:`Technical Lead <rl__technical_lead>` for your problem to establish reporting and planning

process/process_areas/problem_resolution/problem_resolution_workproducts.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,5 +23,5 @@ Work Products Problem Resolution
2323

2424
Problem Resolution Plan (Part of the Platform Management Plan)
2525

26-
.. needextend:: "docs/process/problem_resolution" in docname
26+
.. needextend:: "/process_areas/problem_resolution" in docname
2727
:+tags: problem_resolution

0 commit comments

Comments
 (0)