In a backport PR, there is a link to the primary issue and to the primary issue's CSR request (if it exists), but the backport issue is required to have its own CSR request and that is what the PR should be linking to and checking (if Orahub does that).
More precisely, the linked-to CSR should be one with a fixVersion matching the release in question. A CSR can have multiple fixVersions and in some cases the CSR for the change in the feature release is used for some number of updates too.
More precisely, the linked-to CSR should be one with a fixVersion matching the release in question. A CSR can have multiple fixVersions and in some cases the CSR for the change in the feature release is used for some number of updates too.
- relates to
-
SKARA-1431 The method TestPullRequest#diff sometimes returns wrong information
-
- Resolved
-
-
SKARA-1432 The command `/csr unneeded` doesn't correctly handle an approved CSR
-
- Resolved
-
-
SKARA-1433 The change of the CSR status doesn't force the CheckWorkItem to re-run the check
-
- Resolved
-