Assign a work item to someone

This rule helps ensure that the right people address the right work items at the right time. It takes the manual work out of assigning a team member after a stage in the workflow is complete.  

Jira can change the work item's assignee automatically when you move a work item between columns or change its status:

1. Use the For transition dropdown to tell Jira the column or status that updates the work item's assignee field.
2. Nominate the person who you want to assign the work item to in the Assign to dropdown.

You can assign work items to:

• 報告者。通常は、課題の作成者。
• The current user, or the person updating the work item's status
• No one, making the work item unassigned
• プロジェクト内の特定のユーザー。

例

幅広い領域にわたるチームでは通常、プロセスのさまざまな段階でタスクを割り当てます。たとえば、小規模な機能チームでは、ボードに次のような列が配置されている場合があります。

作業前 → 設計中 → 開発中 → レビュー中 → 完了

You can create rules to assign work items to each discipline across the board:

• For work items moving to In design, assign to the team's designer. They then provide implementation details, specifications, and requirements.

• For work items moving to In development, assign to the team's feature lead. They then write the code or delegate to other developers in the team.

• For work items moving to In review, assign to the team's quality assurance champion. They then provide testing notes or build automated quality tests.

• For work items moving to Done, unassign the work item.

Restrict to when a work item is a specific value

This rule looks at the value of a work item’s field before allowing someone to use a specific transition. This virtual check can help your team better resolve work items by narrowing down the available paths in your workflow based on the information present on the work item. You can use it to enforce best practices for similar work items without having to create a new work type and workflow.

To review the value of a work item’s field before allowing someone to use a specific transition:

1. Use the For transition dropdown to tell Jira Software the transition that checks for the field’s value.

2. Select the field whose value you want to check in the For this field dropdown.

3. Optionally, adjust the Review its value as dropdown to change how you want to evaluate the field (see below for details).

4. Use the Check if it dropdown to select how Jira Software should compare the field’s value (see below for details).

5. Add the value you want to compare against to the This value field.

6. Click Add.

以下として値を確認

Jira Software allows you to evaluate the value entered in a field in a number of different ways. This can be useful when comparing numerals entered as text in a short text field to see if they are equal to an integer, for example.

確認するフィールドの種類に応じて、内容を次のように評価できます。

• a number - any positive or negative number, including decimal values, between -1 trillion and 1 trillion (100000000000000). Keep in mind:

  • このフィールドでは、分数は使用できません。

  • このフィールドでは、小数点のみを区切り文字として使用できます。それ以外の記号 (たとえば桁を示すカンマなど) はルール違反となります。

  • Jira は小数点以下 3 桁以降を四捨五入します。たとえば、5.555555 は四捨五入されて 5.6 となります。 

  • 値の大きな数字は指数表記で入力できます。たとえば、数値 5000 は「5e3」と入力できます。

• a selection - including the available options configured in the field for dropdown and checkbox fields, or user IDs in people fields.

• a time stamp - including a date and, for time stamp fields, a time. We provide a calendar and clock to accurately select the date and time, so you don’t need to know specific formatting.

• text - evaluated as a string, including special and non-Latin characters.

以下の場合はチェック

The selection you make here tells Jira Software how they should evaluate the contents of the field you’re checking. For example, you can check if the value of a number field is greater than or less than a desired value.

確認するフィールドの種類に応じて、以下の演算子を使用してフィールドの値を比較できます。

• contains - for evaluating fields as either a selection or text, this operator looks to see if the desired string or selection is present in the field

• doesn’t contain - for evaluating fields as either a selection or text, this operator looks to see that the desired string or selection is absent from the field

• doesn’t equal - this operator looks to see if the field being evaluated doesn’t exactly match a specific pattern

• equals - this operator looks to see if the field being evaluated does exactly match a specific pattern. For text, the evaluation is case sensitive and considers exact formatting.

• is after - for date and time stamp fields, this operator looks for time stamps that occur after the desired value chronologically

• is before - for date and time stamp fields, this operator looks for time stamps that occur before the desired value chronologically

• is or is after - for date and time stamp fields, this operator looks for time stamps that occur at exactly the same time or after the desired value chronologically

• is or is before - for date and time stamp fields, this operator looks for time stamps that occur at exactly the same time or before the desired value chronologically

• is greater than - for number fields, this operator looks for values that are larger than what’s specified in the rule

• is greater than or equal to - for number fields, this operator looks for values that are either exactly equal to or larger than what’s specified in the rule

• is less than - for number fields, this operator looks for values that are smaller than what’s specified in the rule

• is less than or equal to - for number fields, this operator looks for values that are either exactly equal to or smaller than what’s specified in the rule

Restrict to when a work item has been through a status

This rule helps ensure that work items go through one or more required stages in your team’s workflow. It lets you enforce automated checks in your workflow, and prevents work items from skipping steps in your process. Or, the rule can be set up to do the exact opposite – check that a work item hasn’t been through a particular status.

To check if a work item has been in a status before allowing a specific transition:

1. [トランジション] ドロップダウンを使用して、前のステータスを確認するトランジションを Jira Software に伝えます。

2. Select the status you want to check for in the Check that the work item has been through dropdown.

次のオプションを選択することもできます。

Include the work item’s current status

By default, this workflow rule only looks at prior statuses when evaluating whether to allow a transition. If you want to also evaluate the current status, select the Include the work item’s current status checkbox. This can help prevent looping transitions, where a transition resets the status and it appears unchanged. It keep work items moving down your workflow. Read more about looped transitions below.

このルールを取り消す

You can change the behavior of this workflow rule to check that a work item hasn’t been through a particular status before allowing the transition. This can enforce that bugs or feature requests that have been in a “rejected” status don’t make their way back onto your board.

Only consider the work item’s most recent status

By default, this workflow rule checks the entire history of a work item from its creation in the project. Selecting this option forces the rule to only evaluate the status set just prior to the work item’s current status. In some cases, this may be the same as the current status. We recommend also selecting the Ignore status updates from looped transitions option to ensure the rule evaluates the most recent different status from the work item’s current status.

ループが設定されたトランジションのステータス更新を無視する

Some projects use transitions to trigger notifications, automations in connected apps, or other actions. These transitions usually reset the work item’s status to the current work item status. If you’ve selected to Only consider the work item’s most recent status, the most recent status may be the same as the current status. Selecting the Ignore status updates from looped transitions option forces the rule to evaluate the most recent status that’s different from the work item’s current status.

例

品質保証の例

ここでの目的は、作業が完了する前に品質管理を確実に通過させることです。このような場合、ワークフロー ステータスを使用して、顧客へのデプロイ前に品質保証エンジニアがチームの仕事を検討するよう、チームに実行させるようにします。

たとえば、小規模な機能チームでは、ボードに次のような列が配置されている場合があります。

やること→開発待ち→レビュー中→完了

You can use a workflow status as a quality gate before allowing work to be completed in your project. Add the Check that a work item has been through a status rule to the final transition in your workflow, and you can ensure that work has been reviewed properly by your quality assurance engineer before marking the task as complete:

1. Add a Check that a work item has been through a status rule to the “Any status” transition leading to your “Done” status.

2. In the Check that the work item has been through dropdown, select the “In review” status.

3. Select the Include the work item’s current status option.

4. Select the Only consider the work item’s most recent status option.

5. [ループが設定されたトランジションのステータス更新を無視する] オプションを選択します。

これで、作業はどのステータスでも自由に流れることができます。ただし、最新のステータスが「レビュー中」の場合にのみ「完了」にトランジションできます。

To add extra assurance, you may also add the Restrict who can move a work item rule to this transition, and restrict it to a “Quality assurance engineer” custom role. This way, only people in your “Quality assurance engineer” role can move the work item to done. Learn more about custom roles.

中断されたステータスの例

ソフトウェア チームは、定期的にプロジェクトに参加しているわけではない同僚と相談する必要がある場合があります。たとえば、フロントエンド タスクでは、ユーザー インターフェイスを構築する際に、設計者からのインプットが必要な場合があります。

This type of input isn’t regularly needed in your workflow, but you want to be able to see and check in on the work items that are waiting for your designer’s input.

この場合、「設計待ち」と呼ばれるこのような中断のステータスを作成できます。ワークフローは次のようになります。

You can use the Check that a work item has been through a status rule to ensure the work item goes back to where it came from before the interruption in your normal workflow:

1. 中断された状態用のステータスを作成し、すべてのステータスが新しいステータスに移行できるようにします。上の例では、中断状態を「設計待ち」と呼びます。

2. Create transitions from the interrupted status back to your main workflow. In the diagram above, the “Restart task” and “Back to in progress” transitions direct work items from our “Awaiting design” interrupted status back into the main workflow (TO DO → IN PROGRESS → DONE).

3. Add a Check that a work item has been through a status rule to allow the transition that puts the work item back where it came from. For example, if work items were interrupted while they were “In progress”:

   1. [移行の場合] ドロップダウンで、[処理中に戻る] トランジションを選択します。

   2. In the Check that the work item has been through dropdown, select the “In progress” status.

4. Add a Check that a work item has been through a status rule to prevent the work item moving backward in your workflow. For example, if work items were interrupted while they were “In progress”, you can prevent them from moving back to “To do”:

   1. [移行の場合] ドロップダウンで、[タスクの再起動] トランジションを選択します。

   2. In the Check that the work item has been through dropdown, select the “In progress” status.

   3. このルールを取り消すオプションを選択します。

Now, work items that are interrupted from your main flow and set to “Awaiting design” can only move the following ways:

• work items that move from “To do” to “Awaiting design” can only move back to “To do”.

• work items that move from “In progress” to “Awaiting design” can only move back to “In progress”.

Restrict who can move a work item

This rule helps ensure only the right people can move a work item at a particular point in your team’s process. You can reduce missed steps in your workflow and make sure your team’s work goes through all the people required.

You can restrict who can move a work item to:

• The work item’s assignee.

• The work item’s reporter.

• A user of your choice.

• People in a specific role.

• People in a specific group.
• People with specific permissions.

例

Multi-discipline teams usually have different people working on a task at different stages in their process. For example, a small feature team may have these steps in their process:

作業前 → 設計中 → 開発中 → レビュー中 → 完了

The disciplines in the team may be mapped to roles:

• Designer.

• Software engineer.

• Quality assurance.

Learn more about managing project roles.

Using the rule, they can add these restrictions to make sure the right roles move their work items:

• For work items moving from In design, restrict who can move the work item to the role Designer.

• For work items moving from In development, restrict who can move the work item to the role Software engineer.

• For work items moving from In review, restrict who can move the work item to the role Quality assurance.

Validate that people have a specific permission

This rule looks at what permissions someone has before they’re allowed to use a specific transition. This check helps your team ensure only the right people can move a work item at the right time. Use this rule to secure your workflow based on people’s Jira permissions.

例

A team with a basic workflow might have these statuses in their workflow:

Start → To do → In progress → Done

You can use this rule to validate people have a specific permission by:

• Only allowing people with the Create work items permission to move a work item from Start → To do. This ensures that only the right people can create work for your team.

• Only allowing people with the Assign work items permission to move a work item from To do → In progress. This ensures that whoever starts working on a work item can assign it to someone.

• Only allowing people with the Close work items permission to move a work item from In progress → Done. This ensures that people aren’t able to resolve a work item without being allowed to.

Copy the value of one field to another

Just like the Update a work item field rule, this one also helps ensure your work is updated in the right places at the right time by reducing data entry errors. The key difference is that this rule updates a field based on another field.

You can either copy the value of a field from:

• within the work item itself, which copies a field from a work item to another field on the same work item.

• the parent work item, which copies from the work item’s parent to itself. This option only works if the work item is the child of another work item e.g. copying a work item from an epic (parent) to a story (child), or from a story (parent) to a subtask (child).

When we’ll skip this rule

The information you configure this rule with may not apply to all work types that share the workflow. So we’ll skip this rule when:

• it’s on a work item that doesn’t have both your selected fields (in Copy from this field and To this field).

• it’s configured to copy from the parent work item and the work item doesn’t have a parent.

Don’t worry, this rule being skipped doesn’t mean you’ve done something wrong, or that there’ll be a bug. You’ll be able to go on with your work. It just means there won’t be any fields copied or updated.

How fields are copied

There are three ways a field is copied to another:

• Append: The field’s value is added to the destination field’s value.

• Prepend: The field’s value is added to the start of the destination field’s value.

• Replace: The field’s value replaces the destination field’s value.

Here’s a list of compatible field types and how they’re copied:

Update a work item field

This rule helps ensure that work items capture the right information at the right time. You can reduce data entry errors and increase consistency.

Jira can update certain fields for you automatically when you move work items between columns or change their status:

1. [トランジション] ドロップダウンで、特定のフィールドを更新する列またはステータスを Jira に設定します。
2. 自動更新するフィールドを選択します。

テキスト、数値、ラベル、日付、または期間フィールドやカスタム フィールドなど、プロジェクトに追加したすべてのフィールドを更新できます。カスタム フィールドについては、こちらを参照してください。

挙動には次の違いがあります。

• ルールを使用してテキスト フィールドを更新すると、 Jira は目的のテキストをフィールド内の既存のテキストに追加します。フィールド内の既存のテキストの置き換えは行いません。

• 期間または日付フィールドを更新すると、Jira はボード上のカードの移動時の日付とタイムスタンプ (またはこのいずれか) でフィールド内のすべての要素を置き換えます。静的な時間または日付を指定することはできません。

例

幅広い領域にわたるチームでは通常、プロセスのさまざまな段階でタスクを割り当てます。たとえば、小規模な機能チームでは、ボードに次のような列が配置されている場合があります。

作業前 → 設計中 → 開発中 → レビュー中 → 完了

For traceability and reporting, teams might add custom date fields to their work types to track hand-off dates:

• 設計部門による確認
• 開発への引き継ぎ
• QA 担当者への引き継ぎ

They can create simple rules that update these hand-off date fields to the current date of when someone moves the work item to a certain column or status:

• For work items moving to In design, update the Picked up by design field to the current date/time.
• For work items moving to In development, update the Handed to development field to the current date/time.
• For work items moving to In review, update the Handed to QA champion field to current date/time.

Unknown custom field type

When updating a custom field of a type unknown to the workflow editor, make sure you enter a value that matches the custom field's type. Otherwise, the rule might not work.

You can use these:

• %%CURRENT_USER%%, which will be replaced with the user who transitioned the work item.
• %%CURRENT_DATETIME%%, which be replaced with the date and time of the transition.
• For Select List (cascading) fields, you can either use the value or the id of the option to be selected.

Custom date and time formats

If you’ve set up a custom date and time format and want to configure this rule to update a date and time field, you must enter your desired in the correct format. If this is the case, you’ll see a text field with instructions on how to fill it instead of a date picker field.

For example, you might see a text field that says to enter a date in the “dd/MMMM/yyyy h:mm a” format. One date you could enter would be “15/July/1968 9:30 PM”. To learn more about these formats, check out Java SimpleDateFormat.

To change your date and time formats, you can configure the look and feel of Jira. Learn more about configuring the look and feel of Jira.