Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 931
    • Issues 931
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #17851

Closed (moved)
(moved)
Open
Created Aug 02, 2020 by intrigeri@intrigeriMaintainer9 of 9 tasks completed9/9 tasks

Create a reminder based on GitLab to send e-mail about stalled issues

We should re-implement, in a GitLab-compatible way, the issue triaging tools we had on Redmine to identify:

  • "Stalled work-in-progress"
  • "Reviews waiting for a long time"

This will require a dedicated API key:

  • Decide what level of authorization the user must have → "Reporter" on all projects, in order to be able to see confidential issues
  • Create a GitLab user for ticket triaging
  • Generate an API key
  • Add the API key to the place where it'll be used (ticket triager machine, puppet-tails_secrets_jenkins, puppet-lizard-hiera-node, or what not, depending on where the issue reminder code will run

For more detailed information, pointers, and implementation ideas, see:

  • https://salsa.debian.org/tails-team/gitlab-migration/-/issues/54
  • https://salsa.debian.org/tails-team/gitlab-migration/-/issues/75

Remaining problems after the first trial run, that created #17853 (closed) and #17854 (closed):

  • Summary issues that this creates should be assigned to the ticket gardener → should be the case once tails/gitlab-config!7 is deployed
  • Summary issues that this creates should get appropriate labels (needs tails/gitlab-config!7):
    • at least To Do and T:Communicate
    • perhaps a new, dedicated label, shared by all such automatically created triaging issues?

Finally, once this is all merged & deployed, final cleanup steps:

  • Remove from our Puppet code base all traces of the previous, Redmine-based implementation
Edited Aug 14, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking