Bulk Mutate a List of Issues

Go to Product

Bulk mutate various attributes on issues. The list of issues to modify is given through the id query parameter. It is repeated for each issue that should be modified.

  • For non-status updates, the id query parameter is required.
  • For status updates, the id query parameter may be omitted for a batch "update all" query.
  • An optional status query parameter may be used to restrict mutations to only events with the given status.

The following attributes can be modified and are supplied as JSON object in the body:

If any IDs are out of scope this operation will succeed without any data mutation.

Options

Organization Id or Slug
The id or slug of the organization the issues belong to.
Project Id or Slug
The id or slug of the project the issues belong to.
Id (*)
A list of IDs of the issues to be mutated. This parameter shall be repeated for each issue. It is optional only if a status is mutated in which case an implicit update all is assumed.
Status (*)
Optionally limits the query to issues of the specified status. Valid values are "resolved", "reprocessing", "unresolved", and "ignored".
Body

Request body which must comply to the following JSON Schema:

{
  "type" : "object",
  "properties" : {
    "status" : {
      "type" : "string",
      "description" : "The new status for the issues. Valid values are `\"resolved\"`, `\"resolvedInNextRelease\"`, `\"unresolved\"`, and `\"ignored\"`."
    },
    "statusDetails" : {
      "type" : "object",
      "properties" : {
        "inRelease" : {
          "type" : "string"
        },
        "inNextRelease" : {
          "type" : "boolean"
        },
        "inCommit" : {
          "type" : "string"
        },
        "ignoreDuration" : {
          "type" : "integer"
        },
        "ignoreCount" : {
          "type" : "integer"
        },
        "ignoreWindow" : {
          "type" : "integer"
        },
        "ignoreUserCount" : {
          "type" : "integer"
        },
        "ignoreUserWindow" : {
          "type" : "integer"
        }
      },
      "description" : "Additional details about the resolution. Valid values are `\"inRelease\"`, `\"inNextRelease\"`, `\"inCommit\"`, `\"ignoreDuration\"`, `\"ignoreCount\"`, `\"ignoreWindow\"`, `\"ignoreUserCount\"`, and `\"ignoreUserWindow\"`."
    },
    "ignoreDuration" : {
      "type" : "integer",
      "description" : "The number of minutes to ignore this issue."
    },
    "isPublic" : {
      "type" : "boolean",
      "description" : "Sets the issue to public or private."
    },
    "merge" : {
      "type" : "boolean",
      "description" : "Allows to merge or unmerge different issues."
    },
    "assignedTo" : {
      "type" : "string",
      "description" : "The actor ID (or username) of the user or team that should be assigned to this issue."
    },
    "hasSeen" : {
      "type" : "boolean",
      "description" : "In case this API call is invoked with a user context this allows changing of the flag that indicates if the user has seen the event."
    },
    "isBookmarked" : {
      "type" : "boolean",
      "description" : "In case this API call is invoked with a user context this allows changing of the bookmark flag."
    }
  }
}
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

  • Is Public:
  • Status:
  • Status Details:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Go to Product

Installation

To use this node in KNIME, install the extension Sentry Nodes from the below update site following our NodePit Product and Node Installation Guide:

v5.4

A zipped version of the software site can be downloaded here.

Plugin provider: NodePit
Plugin version: 2.2.0.202407041317
On NodePit since: 2024-12-06
Last update: 2024-12-21
KNIME versions: Since v4.7
NodePit Exclusive Only available on NodePit

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!