An epic should store any content populated within it when a user navigates away, similar to issues
Summary
Epics do not store content that the user has entered. When a user navigates away with unsaved (uncreated) changes, the epic is cleared and empty when they return.
Steps to reproduce
- Open the new epic form
- Enter a title and description
- Navigate someowhere else, like the epic list
- Click back or click "New epic" again
- The epic form is now blank and should be populated with the edits made previously
What is the expected correct behavior?
Epic forms should store content entered, even if not created. This is consistent with how we handle issue creation.
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)