Gitlab Epic Issue Relationships Deleted
status.gitlab.com
Gitlab Epic Issue Relationships Deleted
1–10 of 30 posts
Re: Gitlab Epic Issue Relationships Deleted
#2Re: Gitlab Epic Issue Relationships Deleted
#3Re: Gitlab Epic Issue Relationships Deleted
#4Re: Gitlab Epic Issue Relationships Deleted
#5Re: Gitlab Epic Issue Relationships Deleted
#6Re: Gitlab Epic Issue Relationships Deleted
#7Seems like they have it mostly resolved, the releationships were restored from a backup 3 hours prior to the incident, and they are working to restore the data for the 313 (sic.) items still affected: https://gitlab.com/gitlab-org/gitlab/-/issues/348547
Re: Gitlab Epic Issue Relationships Deleted
#8Seems like they have it mostly resolved, the releationships were restored from a backup 3 hours prior to the incident, and they are working to restore the data for the 313 (sic.) items still affected: https://gitlab.com/gitlab-org/gitlab/-/issues/348547
I am curious, how frequently does GitLab backup their DB? 3 hours seems pretty recent
Re: Gitlab Epic Issue Relationships Deleted
#9I was confused by the title. Apparently epics are a way to organize issues by themes across projects. GitHub doesn't have this concept, in case anyone else was wondering. https://docs.gitlab.com/ee/user/group/epics/ https://github.community/t/epics-github-issues/1430
Re: Gitlab Epic Issue Relationships Deleted
#10I was confused by the title. Apparently epics are a way to organize issues by themes across projects. GitHub doesn't have this concept, in case anyone else was wondering. https://docs.gitlab.com/ee/user/group/epics/ https://github.community/t/epics-github-issues/1430
That's because github isn't trying to be a replacement for JIRA and source control for most teams.
I'm unsure as to whether that's a good thing or not.
1) https://github.blog/2021-06-23-introducing-new-github-issues...