Skip to main content

Espresso Scope Justifications

read:jira-work​

Espresso needs Jira read access to:

  • list Jira field metadata for the numeric field picker;
  • read the two configured source fields on an issue after the transition; and
  • identify the issue and transition needed for the diagnostic outcome.

write:jira-work​

Espresso needs Jira write access to update the configured numeric target field after the configured transition.

The app does not intentionally update other issue fields, comments, attachments, worklogs, links, or transitions.

manage:jira-configuration​

Espresso is registered and configured as a Jira workflow post-function module. This scope is required for the workflow-administration surface and module operation. A prior attempt documented in the repository found that removing it caused Jira to stop invoking the post function even though the configuration UI still rendered.

storage:app​

Espresso uses Forge KVS to retain a bounded diagnostic history of up to 10 recent outcomes for each source1/source2/target field triple. This allows the workflow administrator to see whether an asynchronous post function ran and why a write was skipped or rejected.

The store is diagnostic and bounded, not a complete audit log.