Skip to content

2021-04-30: Create project from group template has been removed from GitLab.com

Current Status

The fix has now been released to GitLab.com as of 14:14 UTC on 2021-05-03. The following workaround is no longer necessary.

We are aware that the “create project from a group template” feature was inadvertently removed from GitLab.com and this has impacted some customers. Impacted customers can work around this issue by using the Import Project functionality, from either "gitlab export” or “repo by URL" (see screenshots below). We expect the fix to be released Monday morning. You may contact GitLab support with any questions.

Workaround

Step 1: Rather than selecting "Create from template", choose "Import project/repository"

image

Step 2: Then, choose either Gitlab export (and import an exported copy of your desired project template), or Repo by URL (and provide the desired git URL and credentials for the template you desire):

image

Timeline

View recent production deployment and configuration events (internal only)

All times UTC.

2021-04-30

  • 17:55 - gitlab-org/gitlab!59083 (merged) deployed to production
  • 18:32 - Customer-internal support case opened
  • 21:30 - Customer reached out to TAM to inquire about missing functionality
  • 22:00 - @jrreid declares incident in Slack.
  • 22:15 - discussion on plans for severity and when to release potential fixes
  • 22:20 - revert MR ready - will be picked in Monday release.

2021-05-03

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

  • ...

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.


Click to expand or collapse the Incident Review section.

Incident Review

Summary

  1. Service(s) affected:
  2. Team attribution:
  3. Time to detection:
  4. Minutes downtime or degradation:

Metrics

Customer Impact

  1. Who was impacted by this incident? (i.e. external customers, internal customers)
    1. ...
  2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
    1. ...
  3. How many customers were affected?
    1. ...
  4. If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
    1. ...

What were the root causes?

  • ...

Incident Response Analysis

  1. How was the incident detected?
    1. ...
  2. How could detection time be improved?
    1. ...
  3. How was the root cause diagnosed?
    1. ...
  4. How could time to diagnosis be improved?
    1. ...
  5. How did we reach the point where we knew how to mitigate the impact?
    1. ...
  6. How could time to mitigation be improved?
    1. ...
  7. What went well?
    1. ...

Post Incident Analysis

  1. Did we have other events in the past with the same root cause?
    1. ...
  2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
    1. ...
  3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
    1. ...

Lessons Learned

  • ...

Guidelines

Resources

  1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)
Edited by Brent Newton