Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,287
    • Issues 44,287
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,282
    • Merge requests 1,282
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #329663
Closed
Open
Issue created Apr 30, 2021 by Felipe Artur@felipe_arturDeveloper

[Feature Flag] Rollout of `block_issue_repositioning`

:block_issue_repositioning has been added on !60141 (merged) to prevent issue manual reordering or rebalance when big project imports are happening.

This is a temporary solution to avoid put database under stress and prevent possible incidents as gitlab-com/gl-infra/production#4321 (closed).

We can remove this as soon as the root cause of the performance issue when importing big projects gets resolved.

Assignee
Assign to
Time tracking