Skip to main content

Espresso Troubleshooting

The target field did not update​

Check in this order:

  1. The workflow change was published.
  2. The issue used the exact transition containing Espresso.
  3. Both source fields contain numeric values.
  4. The target is different from both sources.
  5. The target field context covers the issue's project and issue type.
  6. Open the post function and review Recent runs.

Recent runs says Skipped​

One source field was empty. Espresso does not treat an empty value as zero and writes nothing.

Recent runs says Divide by zero​

For division, Source Field 2 is the denominator. Change the input or choose a different operation.

Recent runs says Field unavailable​

Confirm that:

  • the target field still exists;
  • its context includes the project;
  • its context includes the issue type; and
  • it remains a numeric field accepted by Jira.

Jira error text may still mention an "appropriate screen," but current edit behavior is generally governed by whether the field exists and is associated with the issue context.

Recent runs says Permission denied​

Verify the app installation and granted permissions. A Jira site administrator may need to upgrade/re-consent after a manifest permission change.

Recent runs says Rate limited​

Espresso retries selected rate-limit and transient server failures. If retries are exhausted, wait and test the transition again. Bulk transitions can increase throttling.

No numeric fields appear​

Espresso offers fields Jira reports with schema type number, float, or currency. Confirm the custom field type and that Jira returns schema metadata for it.

The result has more decimal places than expected​

Espresso does not intentionally round. Jira applies the precision supported or configured for the target field. Totesoft must finalize a product rounding policy before claiming a fixed number of decimals.

Watchers received a notification​

Espresso requests notifyUsers=false, but Jira honors suppression only when platform permission and behavior allow it. Treat suppression as best effort, not an absolute guarantee.

Recent runs contains entries from another transition​

The same source1/source2/target field triple shares one history bucket across transitions. Each entry includes the transition name.

The UI says No license or asks to renew​

Espresso's current Marketplace model is Free and the manifest disables licensing. Capture the app version, screenshot, Jira site, and time, then contact support. This indicates a stale or inconsistent build.

Contact support​

Email info@totesoft.com with:

  • Jira site identifier;
  • issue key from a test issue;
  • workflow and transition name;
  • source/target field IDs, but not sensitive values;
  • Recent runs outcome code;
  • approximate time and time zone; and
  • sanitized screenshots.

Do not send passwords, tokens, confidential issue descriptions, or unnecessary field values.