Skip to content

Added severity to issues REST API

Raimund Hook requested to merge srza/gitlab:rest-severity into master

What does this MR do and why?

This change adds severity to the Issues REST API. This field is currently available in the GraphQL API, but invisible to REST users.

In keeping with the GraphQL API, returns the available severities as Uppercased.

Screenshots or screen recordings

{
  "id": 472,
  "iid": 40,
  "project_id": 6,
  "title": "Dismiss Cipher with no integrity",
  "description": "",
  "state": "opened",
  "created_at": "2022-02-21T07:01:21.918Z",
  "updated_at": "2022-03-11T12:31:58.464Z",
  "closed_at": null,
  "closed_by": null,
  "labels": [],
  "milestone": null,
  "assignees": [],
  "author": {
    "id": 6,
    "username": "emerita_gutmann",
    "name": "Caroyln Gorczany",
    "state": "active",
    "avatar_url": "https://secure.gravatar.com/avatar/011a2e614db56e79f3f7fb0c938070f5?s=80&d=identicon",
    "web_url": "REDACTED"
  },
  "type": "INCIDENT",
  "assignee": null,
  "user_notes_count": 0,
  "merge_requests_count": 0,
  "upvotes": 0,
  "downvotes": 0,
  "due_date": null,
  "confidential": false,
  "discussion_locked": null,
  "issue_type": "incident",
  "severity": "UNKNOWN",
  "web_url": "REDACTED/flightjs/Flight/-/issues/40",
  "time_stats": {
...

How to set up and validate locally

  1. Create an incident
  2. query that incident in the REST API

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Raimund Hook

Merge request reports