Skip to main content

Configure Espresso

Jira administration labels can vary by release. The overall workflow is:

  1. Open Jira workflow administration.
  2. Edit the workflow used by the target project/issue type.
  3. Select the transition on which the calculation should run.
  4. Open the transition's post functions or rules.
  5. Add Espresso.
  6. Configure the fields and operator.
  7. Complete Jira's Add/Update action.
  8. Publish the workflow.

Configuration fields​

Source Field 1​

The first numeric operand.

Operator​

Choose Add, Subtract, Multiply, or Divide.

Source Field 2​

The second numeric operand. Order matters for subtraction and division.

Target Field​

The numeric field Espresso updates.

The target cannot be the same as Source Field 1 or Source Field 2. Espresso validates this in the UI and again in the backend before writing.

Saving correctly​

The Espresso iframe includes a Done button for its row. Jira also has an Add/Update action outside the iframe. The shared validation runs when Jira saves the workflow rule, so incomplete or self-referential configurations should be rejected regardless of which action is used.

After changing the workflow, publish the workflow so the post function is active.

Field context​

A numeric field can appear in the global field list but still be unavailable on a particular issue. Ensure the target field's context includes:

  • the project; and
  • the issue type.

A missing context commonly appears in Recent runs as Field unavailable.

Rule identity and Recent runs​

Espresso identifies a diagnostic history by the three field IDs:

source1.source2.target

The transition is not part of the identity. If the same field triple is configured on two transitions, both transitions write to the same 10-entry history bucket. Each entry includes transition information so the runs can be distinguished.

Test before broad use​

Use a controlled workflow and test:

  • positive and negative numbers;
  • decimals;
  • each operator;
  • empty source fields;
  • division by zero;
  • target field context;
  • permission behavior; and
  • rapid or bulk transitions.