New issue from failed job not always working
Summary
When clicking new issue
on a failed job page, a 404 page not found
is shown.
Refreshing the error page still shows the 404 page, but clicking the url and pressing enter opens the new issue page correctly.
When the window is small and the new issue
button is hidden in the menu on the right it works fine.
It appears that the behavior is the same for both the old and new navigation.
Steps to reproduce
Go to a failed job page like https://gitlab.com/ragnar.grootkoerkamp/test/-/jobs/27065101, make sure the window is wide enough for the new issue button to be displayed inline, and click it.
What is the current bug behavior?
A 404 page not found
is shown
What is the expected correct behavior?
New issue page should open with correct values prefilled.
Output of checks
Happens on gitlab.com
Error message
On my local gitlab instance, the following message is shown in production.log
:
ActionController::RoutingError (No route matches [POST] "/ragnar/project_name/issues/new"):
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/connection_rack_middleware.rb:31:in `call'