Issues to apply severity and priority for Geo

Hi @rnienaber,

Here is a list of bugs without severity and priority for the team.

We would like to ask you to:

Work with your team to triage and add a severity label (~S1 / ~S2 / ~S3 / ~S4) and a priority label (~P1 / ~P2 / ~P3 / ~P4) to the issues in this list.

The definition of these labels are defined at:

  • Priority Labels
  • Severity Labels

For the issues triaged please check off the box in front of the given issue.

Please work with your team to complete the list this week.

  • Geo::RenameRepositoryWorker: NoMethodError: undefined method `date' for nil:NilClass ~"Geo", ~"Gitaly", auto updated, ~"bug"
  • Improve Geo failures API handling of unknown types ~"Geo", Geo Administration, api, ~"bug"
  • Hashed storage specs use development repositories ~"Geo", ~"Geo Validation/Accuracy", ~"bug", test
  • Geo: MetricsUpdateWorker timing out on counting unverified Wikis ~"Geo", ~"Geo Performance", ~"bug", database, ~"no-priority", ~"no-severity", ~"performance"
  • [Geo] Invalid repositories can't be synced GCP Migration, ~"Geo", ~"Geo Replication/Sync", ~"P3", ~"bug", ~"no-severity"
  • Geo: Ensure two git processes can't write in parallel to the same repository ~"Geo", ~"Geo Replication/Sync", ~"bug", ~"no-priority", ~"no-severity"
  • Geo: After DB went down and back up, large number of ProjectImportScheduleWorker jobs ran ~"Geo", Geo Administration, ~"bug", ~"no-priority", ~"no-severity"
  • Geo: Inconsistent database replication status when Wal-E streaming is in use GCP Migration, ~"Geo", Geo Administration, ~"bug", ~"no-priority", ~"no-severity"
  • Geo: Job artifact deleted event could not be created ~"Geo", ~"Geo Validation/Accuracy", Object Storage, ~"bug", ~"no-priority", ~"no-severity"
Edited Oct 02, 2018 by Rachel Nienaber
Assignee Loading
Time tracking Loading