Totesoft Documentation

Espresso Release Checklist

Build and static validation

• Clean clone and npm ci succeed.
• npm run contract:check succeeds.
• npm test succeeds.
• npm run lint succeeds.
• npm run build succeeds from a clean Custom UI install.
• forge lint is clean.

Functional behavior

• Install on a clean Jira Cloud test site.
• Create, edit, view, and delete/re-add a workflow rule.
• Publish workflow changes.
• Test Add, Subtract, Multiply, and Divide.
• Test number, float, and currency field schemas.
• Test positive, negative, decimal, and large finite values.
• Test empty Source 1 and Source 2.
• Test divide by zero and non-finite result protection.
• Confirm target cannot equal either source.
• Test target field outside the project/issue-type context.
• Test permission failures.
• Test rate limiting and retry exhaustion.
• Verify notifyUsers=false behavior on controlled transitions.
• Confirm no customer-facing license warning appears in the Free build.

Recent runs

• Verify newest-first order and maximum 10 entries.
• Verify same field triple on two transitions shares one bucket and shows transition names.
• Verify concurrent-run behavior is acceptable for a diagnostic tail.
• Verify every backend exit produces one outcome.
• Verify no numeric source or result value is an explicit stored field.
• Verify raw Jira error bodies are sanitized before storage and normal logging.

Logs and privacy

• Review normal production logs with ESPRESSO_DEBUG absent/false.
• Review debug logs with ESPRESSO_DEBUG=true on synthetic data only.
• Disable debug immediately after the test.
• Confirm no external egress or analytics.
• Test uninstall/reinstall and document current Forge retention/relink behavior.
• Update privacy notice and Marketplace answers from observed behavior.

Public release

• Marketplace payment model is Free.
• No “renew subscription” or “No license” customer wording remains.
• Documentation, support, privacy, and terms links return HTTP 200.
• Provider terms HTML validates and contains no unsupported product obligations.
• Privacy policy accurately describes shared history identity and stored detail.
• Screenshots contain synthetic data.
• Privacy and Security tab is complete.