Totesoft Documentation

Getting Started with Espresso

What Espresso does

Espresso calculates one Jira numeric field from two other numeric fields when an issue completes a configured workflow transition.

For example:

Estimated Hours + Additional Hours -> Total Hours

Quantity x Unit Price -> Total

Requirements

You need permission to edit Jira workflows. The relevant numeric fields must exist and be available for the project and issue types that use the workflow.

Espresso’s field picker includes schemas Jira reports as:

• number;
• float; or
• currency.

Execution timing

Espresso is a post function. The workflow transition completes first, and the calculated target value can appear shortly afterward.

Espresso does not:

• recalculate on every ordinary field edit;
• run on transitions where it was not configured;
• backfill old issues automatically; or
• treat an empty source field as zero.

Calculation rules

Supported operators:

Operator	Example
Add	A + B
Subtract	A - B
Multiply	A x B
Divide	A / B

The target field cannot also be either source field. Division by zero is rejected. Espresso writes the computed finite number without intentionally rounding it; Jira controls the precision accepted or displayed by the target field.

First example

1. Create three Jira numeric fields: Quantity, Unit Price, and Total.
2. Ensure all three field contexts cover the test project and issue type.
3. Edit the workflow and select a test transition.
4. Add Espresso as a post function.
5. Configure Quantity x Unit Price -> Total.
6. Publish the workflow.
7. Populate Quantity and Unit Price on a test issue.
8. Complete the configured transition.
9. Confirm Total is updated and open the rule’s Recent runs panel.