Cannot set milestone on Incidents
Summary
If you have an existing issue and change it to an incident, you cannot update the milestone and would get this error message.
Failed to set milestone on this merge_request. Please try again.
From what I gather form this issue, we should be able to assign milestones to incidents.
Steps to reproduce
- Create a blank project
test_project
. - Create a milestone
test_milestone
. - Create an issue
issue 01
and assign the previously created milestonetest_milestone
. - Edit the issue
issue 01
and change it to anIncident
. - Observe that the milestone is cleared. Try setting it and get the error message
Failed to set milestone on this merge_request. Please try again.
Example Project
https://gitlab.com/kballon_ultimate_group/zd527484_incident_milestone/-/issues/incident/2
What is the current bug behavior?
- Users cannot update the milestone of an incident.
- Users receive a misleading error message.
What is the expected correct behavior?
- Users should be able to update the milestone of an incident.
- Users should not receive an error message.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)