Promote Issue to an Epic within GitLab.org / Inbound Marketing

Summary

https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/783

I was trying to promote this issue to an epic, but I got the following error message:

PG::CheckViolation: ERROR: new row for relation "resource_state_events" violates check constraint "state_events_must_belong_to_issue_or_merge_request_or_epic" DETAIL: Failing row contains (17847621, 1499790, 76210103, null, 2021-01-04 21:05:43.095023+00, 2, 174376, null, f, f, null).

Steps to reproduce

Example 1: I clicked on promote to epic within the horizontal hamburger menu from the issue link above.

Example 2:

  1. Create an issue on Group A / Project 1
  2. Promote the issue to epic (works) Epic is now under Group A
  3. Delete the epic
  4. Reopen the issue
  5. Move the issue to Group A / Subgrup B / Project 2
  6. Attempt to promote the issue to epic will result in the error

Attempting to promote a clone of the issue will result in the same error (#296567 (comment 551635544))

Example Project

What is the current bug behavior?

What is the expected correct behavior?

I want this issue to be an epic.

Relevant logs and/or screenshots

Screen_Shot_2021-01-04_at_1.23.05_PM

Output of checks

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)

Possible fixes

Edited by John Hope