Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9643

Closed
Open
Created Sep 18, 2015 by Administrator@rootOwner

MergeRequestsController thrown a Error 500 when you delete the assiociated milestone

Created by: ArKam

Hi team, I've just detected a quite strange behavior on my current installation of GitLab.

Is that normal that if you delete a milestone attached to a list of merge requests the complete view goes on the ERROR 500 Realm?

I mean, don't gitlab should either deny any remove of the milestone if there is some items still attached to?

For now, if I go to my merge_requests view, I've got a Error 500 with the following message showing on the production.log file:

https://gist.github.com/ArKam/339ab337c075f855a6ff

Is there a workaround to find out what was the removed milestone ID/Title and then reinject it on the database?

Assignee
Assign to
Time tracking