Skip to content

Unable to create new issues in project, getting 500's

I am currently getting 500 errors when trying to create new issues in https://gitlab.com/gitlab-com/Product/-/issues/new. Every time I submit, It pauses for 15 seconds or so and then generates a 500 error. I have tried this about 10 times, just recently as well as a few hours ago, with the same result.

It appears other users are not affected by this problem, as new issues have since been created in that project.

Unfortunately nothing I have tried seems to have resolved the problem:

  • Signing in to GitLab in a different browser and creating an issue
  • Waiting 5-6 hours
  • Retrying over and over again

Details:

Form submission details:

MIME Type: application/x-www-form-urlencoded
utf8: ✓
authenticity_token: REDACTED
issue[title]: Align on PI convention and content
issue[description]: Currently on the performance indicator pages, we have two fields: `instrumentation` and `health` (shown as `status`).
 
 Today, there is variation between sections on how to capture the insights/learnings and actions being taken as a result. We should consider standardizing and defining how to document these in the YAML.
 
 * The Secure/Defend sections has taken one step in his direction with: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61312/diffs
 * Dev, Ops, and Enablement sections are using a convention of prefixing reasons with `Insight -` and `Improvement -` without any further YAML changes.
 Other
 
 ### Proposal
 
 As a first step, we should align on what information we want to convey and in what sections.
 
 I think of these meetings as covering three topics:
 
 * Status: Progress towards achieving documented goal, what is currently being done to achieve
 * Health: R/Y/G based on tracking towards goal
 * List of improvements/actions being taken to attain goal
 * Insights: List of coupled insights and actions being taken based on performance indicators, may be secondary PI's or other insights unrelated to primary goal
 * Insight: Narrative on an insight we had, link to chart if not PPI
 * Action: Action being taken based on insight. Could be additional instrumentation, deeper analysis, product change, etc.
 * Instrumentation: Progress towards instrumentation completion
 * Status: R/Y/G indicator
 * Narrative on what is happening to complete instrumentation, if not complete
 
 Based on this, we can derive the simplest YAML format.
issue[confidential]: 0
issue[assignee_ids][]: 0
issue[epic_id]
issue[label_ids][]
issue[weight]
issue[due_date]
issue[issue_type]: issue
issue[lock_version]: 0