新しいワークフロー エディターとは
The workflow editor allows admins to define, customize, and manage how work items move through various stages of work. It visualizes the flow of work, allowing you to add statuses, transitions and rules to define operations or conditions in the flow.
You can use the workflow editor to automate routine actions, apply business rules, and configure different work item paths based on project or work type requirements.
What’s changed in the new editor
The new workflow editor has all the same actions as the old experience, but it’s now in one place. From a single view, you can configure statuses, transitions, and transition rules without having to navigate around Jira, or multiple tabs.
ツールバー: ステータス、トランジション、ルールを追加してワークフローを作成します。
更新または破棄: 変更を即座に公開します。変更内容が期待どおりではない場合、いつでも破棄して元のワークフローに戻すことができます。
Details: Select a status or transition from the diagram and edit its name, rules, properties, and more.
Diagram: Drag to move statuses and create transitions. Select a status or transition to see its details.
Relevant projects: See which projects use the workflow before you publish.
Key differences
Edit and publish instantly
A key difference with the new editor is that it doesn’t use draft workflows.
In the old editor, changes were made across multiple pages and stored in a draft until you were ready to publish. In the new editor, admins only ever edit the published workflow. Changes are now all made in the same view and can be published by selecting Update workflow, or discarded.
A big benefit of this is that the new editor doesn’t have the same limitations around active workflows as the old editor.
これは次のことを意味します。
you can delete statuses in active workflows, and
if a status has no outgoing transitions (not including global transitions), new outgoing transitions can be added (regular or global).
You no longer need to copy the workflow, make changes, and then update the workflow schemes to activate it. It’s all one editing experience.
Delete statuses and update work items
When you delete a status in your workflow, you’ll immediately be taken through steps to move work items from that deleted status to a new status.
Know which projects use your workflow
Before you publish your workflow, you want to make sure you’re updating the right projects, and now, you can do it right from the workflow editor itself.
Share transitions as you create
In the new editor, you can create transitions for work items in multiple statuses with a single set of rules and properties.
In the old editor, you could do this by creating a transition between two existing transitions, then applying that transition to other statues via Add transition, then Reuse transition.
In the new editor, you can apply a transition to multiple statuses by selecting multiple From statuses when you create the transition or edit an existing status.
Easily add rules to a transition
Rules is where you’ll find conditions, validators, and post-functions, with updated terminology (restrict, validate, and perform action). These operations created while using the old editor should be retained when moving to the new editor.
These are the new workflow editor’s rules:
Conditions → Restrict transition
Validators → Validate details
Post-functions → Perform actions
The new editor's rules provide the same conditions, validators, and post-functions as the old editor, they’ve just been combined and renamed.
Use these rules to limit when your team can use a transition, or to automatically perform an action as they do.
This table shows how rules map between the old editor and the new editor.
Old editor | 新しいエディタ |
---|---|
条件 | |
担当者のみ条件 | 作業項目を移動できるユーザーを制限する |
報告者のみ条件 | |
権限条件 | |
グループ内のユーザー | |
任意のグループのユーザー | |
プロジェクト ロール内のユーザー | |
任意のプロジェクト ロールのユーザー | |
カスタム フィールドのユーザー | |
グループ カスタム フィールドのユーザー | |
値フィールド | Restrict to when a field is a specific value |
数値カスタム フィールドの比較 | |
前のステータス条件 | Restrict to when a work item has been through a specific status |
割り当てからの分離条件 | Restrict users who have previously updated a work item’s status |
サブタスクに応じたブロック条件 | Restrict based on the status of subtasks |
承認されるまでトランジションをブロック | 承認されるまでトランジションをブロック |
ユーザーに非表示条件 | Restrict from all users |
常に False 条件 | |
Validators (and screen configuration) | |
必須フィールド バリデーター | Validate a field |
フィールドの変更有無バリデーター | |
フィールド単一値バリデーター | |
日付比較バリデーター | |
日付枠バリデーター | |
正規表現チェック | |
Forms: Forms attached | Require a work item to have a form attached |
Forms: Forms submitted | Require form submission on a work item |
親ステータス バリデーター | Validate that parent work items are in a specific status |
権限バリデーター | ユーザーが特定の権限を持っていることを確認する |
前のステータスバリデーター | Validate that a work item has been through a specific status |
ユーザー権限の検証 | Sunsetted. Use the Validate that people have a specific permission rule. |
Screen field (in transition details) | 画面を表示 |
Post-functions | |
課題フィールドの更新 | Update a work item’s field |
課題のカスタム フィールドの更新 | |
フィールド値のクリア | |
現在のユーザーへの割り当て | Assign a work item |
開発リーダーへの割り当て | |
報告者への割り当て | |
Update Issue Field (for assignee field) | |
他のフィールドの値をコピー | あるフィールドの値を別のフィールドにコピーする |
ユーザーのプロジェクト ロールに基づいた課題セキュリティ レベルの設定 | Set a work item’s security level |
Webhook をトリガーする | Trigger a webhook |
Want to learn about the old editor? Read how to manage workflows in the old editor.
この内容はお役に立ちましたか?