Skip to content
GitLab
项目 群组 主题 代码片段
  • /
  • 帮助
    • 帮助
    • 支持
    • 社区论坛
    • 提交反馈
  • 登录
  • L large
  • 项目信息
    • 项目信息
    • 动态
    • 标记
    • 成员
  • 仓库
    • 仓库
    • 文件
    • 提交
    • 分支
    • 标签
    • 贡献者统计
    • 分支图
    • 比较修订版本
  • 议题 21
    • 议题 21
    • 列表
    • 看板
    • 服务台
    • 里程碑
  • 合并请求 12
    • 合并请求 12
  • CI/CD
    • CI/CD
    • 流水线
    • 作业
    • 产物
    • 计划
  • 部署
    • 部署
    • 环境
    • 发布
  • 软件包与镜像库
    • 软件包与镜像库
    • 软件包库
    • 容器镜像库
    • Terraform 模块
    • 模型实验
  • 监控
    • 监控
    • 事件
  • 分析
    • 分析
    • 价值流
    • CI/CD
    • 仓库
  • Wiki
    • Wiki
  • 代码片段
    • 代码片段
  • 动态
  • 分支图
  • 创建新议题
  • 作业
  • 提交
  • 议题看板
收起侧边栏
  • 王权利
  • large
  • 议题
  • #5179

[6.1] Issues renumbering

Created by: sashkab

With 6.1 update I was surprised, that GitLab decided to brake everything and introduce project-related ids for issues, merge requests. This broke a lot of things:

  • comments in commits mention old issue numbers;
  • issues mention old issue numbers, but they weren't translated to new id;
  • same thing with merge requests.

From one point of view, global IDs where issue. From other, when performing upgrades, GitLab could have kept old issue/merge ids for existing projects. I don't understand, why you couldn't have kept IDs same, despite making them project related?

I «fixed» this with UPDATE issues SET iid=id;. Seems to work for me, but will this cause any issues, I'm not aware of? I didn't have to update merge_requests table, but it can be updated same way: UPDATE merge_requests SET iid=id;

Why brake what's working?

指派人
分配到
工时统计