Project

General

Profile

coordination #69310

[epic] SUSE QA tools team ticket process helpers

Added by cdywan 6 months ago. Updated about 1 month ago.

Status:
Blocked
Priority:
Normal
Assignee:
Target version:
Start date:
2020-07-24
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)

Description

Motivation

We want to follow the https://progress.opensuse.org/projects/openqav3/wiki#ticket-workflow including https://progress.opensuse.org/projects/qa/wiki#How-we-work-on-our-backlog which define some SLOs for ourselves which are hard and tedious to track as humans but bots would be happy to do that job.

Ideas

  • Query Redmine via GitLab CI bot to update due date: On GitHub we have bots checking that certain parameters are met, such as stale PRs or conflicts. It would be great to update the Due Date automatically according to tickets that need updates, taking priority into account, which then allow Redmine to send out notifications. As an alternative write comments directly.

Subtasks

action #69322: Automatic check for SUSE QA tools WIP-Limit based on ticketsResolvedokurz

action #73468: SUSE QA tools team ticket process helpers: Set due date on tickets in redmine based on SLOsResolvedilausuch

action #81106: test out rocket chat notifications from github actionsWorkable

History

#1 Updated by okurz 6 months ago

  • Subject changed from Query Redmine via GitLab CI bot to update due date to [epic] SUSE QA tools team ticket process helpers
  • Description updated (diff)
  • Category set to Organisational
  • Target version set to Ready

thanks for the reminder. For anyone else reading this: This ticket is based on a discussion that cdywan and me had this morning about how to help ourselves better in our workflows.

#2 Updated by okurz 6 months ago

  • Due date set to 2020-07-24

due to changes in a related task: #69322

#3 Updated by okurz 6 months ago

  • Status changed from New to Blocked

I have created one specific example in a subtask #69322 that should be easy enough to be implemented and can provide us feedback if this is way we should follow for further work in this direction.

#4 Updated by okurz 4 months ago

  • Description updated (diff)

The team's WIP-limit is checked based on #69322 . This seems to work out fine so far. Additional checks could be added

#5 Updated by szarate 3 months ago

  • Tracker changed from action to coordination
  • Status changed from Blocked to New

#6 Updated by szarate 3 months ago

#7 Updated by okurz 3 months ago

  • Status changed from New to Blocked

new specific subtask created, waiting for that

#8 Updated by okurz about 1 month ago

  • Project changed from openQA Project to QA
  • Category deleted (Organisational)

Also available in: Atom PDF