Workflows
Manages the available workflows in Jira, which define the sequence of statuses and transitions for issues.
Select
Most filters are processed client side, though there are a few exceptions to this:
- The connector uses the Jira APIs to process filters on the Name that use the equals (=) and IN operators only.
- The connector processes WHERE filters for the IsActive and Query columns with only the equals (=) operator server-side.
For example, the following queries are executed server side:
SELECT * FROM Workflows WHERE Name = 'abc'
SELECT * FROM Workflows WHERE Name IN ('abc','def','ghi')
SELECT * FROM Workflows WHERE IsActive = true AND Query = 'flow'
The Scope, Statuses, and Workflows columns accept aggregate values and are only used for inserting to and updating Workflows.
INSERT INTO Workflows(Scope, Statuses, Workflows) VALUES ('{"type":"GLOBAL"}', '[{"description":"","name":"To Do #2","statusCategory":"TODO","statusReference":"f0b24de5-25e7-4fab-ab94-63d81db6c0c0"}]', '[{"description":"","name":"Software workflow 1","startPointLayout":{"x":-100.00030899047852,"y":-153.00020599365235},"statuses":[{"layout":{"x":114.99993896484375,"y":-16},"properties":{},"statusReference":"f0b24de5-25e7-4fab-ab94-63d81db6c0c0"}],"transitions":[{"actions":[],"description":"","from":[],"id":"1","name":"Create","properties":{},"to":{"statusReference":"f0b24de5-25e7-4fab-ab94-63d81db6c0c0"},"triggers":[],"type":"INITIAL","validators":[]}]}]')", true)
Columns
| Name | Type | ReadOnly | References | SupportedOperators | Platform | Description |
| Id | String | False | Common |
The unique identifier of the workflow within Jira. This ID is used internally and in API operations to reference the workflow. | ||
| Name | String | False | IN | Common |
The name assigned to the workflow, which typically reflects the process or team it supports (for example, 'Software Development Workflow'). | |
| Description | String | False | Common |
A user-defined explanation of what the workflow represents or how it should be used. Helpful for distinguishing between similar workflows. | ||
| Created | String | False | Common |
The timestamp indicating when the workflow was initially created. | ||
| Updated | String | False | Common |
The timestamp indicating the most recent update to the workflow. Reflects configuration or metadata changes. | ||
| IsDefault | Boolean | False | Common |
Deprecated on Cloud instances. If the value is 'true', the workflow is currently designated as the default workflow for its associated issue type or project. | ||
| CanDelete | Boolean | False | Common |
Deprecated on Cloud instances. If the value is 'true', the workflow can be deleted by users with appropriate permissions. Some system workflows cannot be deleted. | ||
| CanEdit | Boolean | False | Common |
If the value is 'true', the workflow can be edited. This can be restricted based on permissions or if the workflow is active. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| IsActive | Boolean |
If the value is 'true', the workflow is currently in use by one or more projects. Active workflows can be subject to restrictions for modification or deletion. |
| Query | String |
Used in search queries to filter workflows by name. Supports case-insensitive, partial string matching. |
| Scope | String |
A JavaScript Object Notation (JSON) object defining the scope of the workflow, such as whether it is global or limited to specific projects. This is write-only and does not appear in SELECT statements. |
| Statuses | String |
A JSON object specifying the statuses included in the workflow. Used during workflow creation or updates to define transitions and state logic. |
| Workflows | String |
A JSON object containing the full workflow configuration. Used for bulk creation or update of workflows and not returned in SELECT queries. |