If your team plans in Jira, Malveon reads from it so Malvedeck can compute real project health, and it can create issues back.
What it reads
Malveon requests read access to Jira work items and the users on them (the jira-work and jira-user scopes). That task data feeds the Malvedeck health engine: completion, delays, and blockers.
What it writes
Through the same Atlassian connection, Malveon can create Jira issues where you ask it to. The connection is bidirectional.
Security
Jira webhooks are verified with an x-hub-signature HMAC (SHA-256 based) before processing. Tokens are encrypted at rest with AES-256-GCM, and the OAuth flow uses a signed state value to prevent forged callbacks.