Please enable JavaScript to view this site.

Made in EU
JIRA Cloud Forums

JIRA Cloud API Data Model

Navigation: Schema: Core > Tables

WorkflowSchemes: JIRA Cloud Workflow Schemes

Catalog: JIRA

Schema: Core

Primary Keys: id

Label: Workflow Schemes

This is a read-only table. The JIRA Cloud API may not support changing the data or the Invantive SQL driver for JIRA Cloud does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the JIRA Cloud API.

Select JIRA Cloud API URL: /workflowscheme

Insert JIRA Cloud API URL: /workflowscheme

Update JIRA Cloud API URL: /workflowscheme

Delete JIRA Cloud API URL: /workflowscheme

Field Selection Method: NotRequired

Base Path: values[*]

Table Columns

The columns of the table WorkflowSchemes are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

defaultWorkflow

string

 

☐

The name of the default workflow for the workflow scheme. The default workflow has All Unassigned Issue Types assigned to it in Jira. If defaultWorkflow is not specified when creating a workflow scheme, it is set to Jira Workflow (jira).

description

string

 

☐

The description of the workflow scheme.

draft

boolean

 

☐

Indicates whether the workflow scheme is a draft or not.

id

int64

 

☐

The ID of the workflow scheme.

issueTypeMappings

string

 

☐

The issue type to workflow mappings, where each mapping is an issue type ID and workflow name pair. Note that an issue type can only be mapped to one workflow in a workflow scheme.

issueTypes

string

 

☐

The issue types available in Jira.

lastModified

string

 

☐

The date-time that the draft workflow scheme was last modified. A modification is a change to the issue type-project mappings only. This property does not apply to non-draft workflows.

lastModifiedUser_accountId

string

 

☐

The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5. Required in requests. An account ID with value unknown is returned when there is missing data for a user, which only happens for deleted users. We recommend you treat this value as an error case if you need to access more information about the user.

lastModifiedUser_accountType

string

 

☐

The user account type. Can take the following values: atlassian regular Atlassian user account, app system account used for Connect applications and OAuth to represent external systems, customer Jira Service Desk account representing an external service desk

lastModifiedUser_active

boolean

 

☐

Indicates whether the user is active.

lastModifiedUser_displayName

string

 

☐

The display name of the user. Depending on the user’s privacy setting, this may return an alternative value.

lastModifiedUser_emailAddress

string

 

☐

The email address of the user. Depending on the user’s privacy setting, this may be returned as null.

lastModifiedUser_key

string

 

☐

This property is no longer available and will be removed from the documentation soon

lastModifiedUser_locale

string

 

☐

The locale of the user. Depending on the user’s privacy setting, this may be returned as null.

lastModifiedUser_name

string

 

☐

This property is no longer available and will be removed from the documentation soon.

lastModifiedUser_timeZone

string

 

☐

The time zone specified in the user's profile. Depending on the user’s privacy setting, this may be returned as null.

name

string

 

☐

The name of the workflow scheme. The name must be unique. The maximum length is 255 characters.

originalDefaultWorkflow

string

 

☐

For draft workflow schemes, this property is the name of the default workflow for the original workflow scheme. The default workflow has All Unassigned Issue Types assigned to it in Jira.

originalIssueTypeMappings

string

 

☐

For draft workflow schemes, this property is the issue type to workflow mappings for the original workflow scheme, where each mapping is an issue type ID and workflow name pair. Note that an issue type can only be mapped to one workflow in a workflow scheme.

updateDraftIfNeeded

boolean

 

☐

ndicates whether to create or update a draft workflow scheme when updating an active workflow scheme. An active workflow scheme is a workflow scheme that is used by at least one project.

 

19-12-2022 16:35 Version 22.1.113-BETA+3734

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer