What Is Issue In GitLab?

What's Happening

GitLab's Issues Boards are essentially Kanban boards that map columns to labels like To Do, In Progress, and Done. When issues carry those labels, they automatically land in the right column. If your board looks blank or frozen, three things usually go wrong: your browser's serving an old cached version, the board labels got messed up, or someone changed your project permissions. GitLab's own docs explain that the board depends on label settings under Project → Issues → Labels, where each active label needs to be marked as a Board label to show up on the board GitLab Issue Boards Docs.

Step-by-Step Solution

1. Refresh the board view.
   • Windows/Linux: Ctrl + Shift + R
   • Mac: Cmd + Shift + R
   • This forces your browser to skip the cache and fetch the freshest version of the board.
2. Verify label mapping.
   1. Head to Project → Issues → Labels.
   2. Double-check that at least one label (like To Do) is enabled as a Board label.
   3. If none are enabled, edit the label and flip on the Board label toggle.
   4. Save your changes and refresh the board.
3. Reset board visibility.
   1. Go to Project → Settings → General → Visibility, project features, permissions.
   2. Under Project features, turn off Issues.
   3. Wait about 10–15 seconds, then turn it back on.
   4. Reload the page to reload the board with default settings.
4. Check user permissions.
   • Visit Project → Settings → Members.
   • Make sure your role has Issues: Read & Write access.
   • Owners should double-check that no one accidentally changed anyone's role.
5. Inspect browser console.
   • Right-click the page → Inspect → Console.
   • Look for red errors like Failed to load issues or CORS/403 issues.
   • (Sometimes VPNs or network blocks prevent the API calls from going through.)

If This Didn’t Work

• Switch to classic issue view.
  1. Go to Project → Issues.
  2. Click the dropdown next to New issue.
  3. Pick Switch to classic view.
  4. This shows a simple list of issues instead of the Kanban board.
• Manually clear GitLab cache (Admin only).

  On your GitLab server, run these commands:

  1. sudo gitlab-rake cache:clear
  2. sudo gitlab-ctl restart
  3. This wipes all cached issue board data and restarts the application.

  See: GitLab Cache Rake Tasks

• Test in a private browsing window.
  • Open an incognito or private window.
  • Log into GitLab and go to the project.
  • If the board loads now, your main browser profile is the problem—clear cookies and cache.

Prevention Tips

• Label governance. Assign someone to review project labels every month. Delete duplicates and make sure every label used on the board is marked as a Board label. Use Project → Issues → Labels to clean things up. GitLab Label Management
• Browser hygiene. Clear GitLab cookies every 30 days via Settings → Privacy → Clear browsing data → Cookies and other site data. Set Chrome or Edge to clear cache on exit in Settings → Privacy. Chrome Cache Settings
• Role audits. Run a quarterly permissions review using Project → Settings → Audit Events to spot any role changes. Remove inactive members to cut down on permission conflicts. GitLab Audit Events
• Backup labels and boards. Export project labels via API using curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/5/labels" and save the JSON in a shared drive. Restore them later via Project → Settings → Import and export → Labels. GitLab Labels API
• Monitor API limits. GitLab caps requests at 6,000 per minute. If your automation scripts hit 429 errors, add delays or use pagination in API calls. GitLab Rate Limits