Project

General

Profile

Actions
Copy link

coordination #93871

open

[epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incident

Added by jkohoutek almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
future
Start date:
2020-12-04
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)

Description

The coordinators changing the process, so the packages hat belong together should be in one incident.

Introduced in S:M:19483:242960
SLE 15 sbd 1.4.1+20200807.883c2f8-3.11.2 -> 1.4.1+20200807.883c2f8-3.14.2
SLE 15 SP1 sbd 1.4.1+20200807.883c2f8-3.9.2 -> 1.4.1+20200807.883c2f8-6.1
SLE 15 SP2 sbd 1.4.1+20200807.883c2f8-3.3.2 -> 1.4.1+20200807.883c2f8-7.1

Subtasks 3 (1 open — 2 closed)

action #93931: [tools][qem] MTUI support multiple versions of package in incidentResolvedosukup2021-06-14

Actions
action #93934: [tools][qem] template generator - multiple package version in incidentResolvedjbaier_cz2020-12-04

Actions
action #93937: [tools][qem] qamapi - incidents can have multiple versions packagesNew2021-06-14

Actions

Related issues 1 (0 open — 1 closed)

Related to QA - action #80690: [qem] Testing of packages in different codestreams but in one incidentResolvedjbaier_cz2020-12-03

Actions
Actions
Copy link
 #1

Updated by okurz almost 3 years ago

  • Target version set to Ready

thank you. so do you plan to create subtickets for the individual tools that need changing? I think we just have to do it. But having tickets can at least explain to others why we don't do other stuff in the meantime :)

Actions
Copy link
 #2

Updated by jbaier_cz almost 3 years ago

  • Related to action #80690: [qem] Testing of packages in different codestreams but in one incident added
Actions
Copy link
 #3

Updated by okurz almost 3 years ago

  • Tracker changed from action to coordination
  • Subject changed from Change in the maintenance requests - improve of the process to submit packages that belong together in one incident. to [epic] Change in the maintenance requests - improve of the process to submit packages that belong together in one incident.
Actions
Copy link
 #4

Updated by hrommel1 almost 3 years ago

  • Subject changed from [epic] Change in the maintenance requests - improve of the process to submit packages that belong together in one incident. to [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incident

I have updated the title to reflect the driving force behind this change.

The agreement with Maintenance Coordination and Security is that we want to work towards allowing packages from different code streams within a single incident as long as the fix set / features list is identical. Hence the resulting test plan would be very similar.

Apart from adaptions to be done on the tooling side, we might run into situations where we can not finish testing on all affected code streams/products in time. If that happens, the Maintenance Coordination or Security team might decide if to break down the incident into smaller pieces.

Actions
Copy link
 #5

Updated by okurz almost 3 years ago

  • Assignee deleted (osukup)
  • Target version changed from Ready to future

We need to clarify what is needed and what can be done without relying on single individuals hence unassigning osukup and moving out of the current backlog

Actions
Copy link

Also available in: Atom PDF