What Cymph uses it for
Cymph connects to JIRA to read project and issue metadata, and to create issues from playbook content. This connector performs both read and write operations.
JIRA and Confluence are separate integration types but share the same Atlassian API token mechanism. The token must be created for the right app and carry the scopes listed below. Requirements
Token setup
Follow the instructions provided here to generate a token. The token must be created for the JIRA app and have the appropriate scopes for reading and creating issues.
Permissions
The following scopes are required:
Or, if you are using classic scopes:
An Atlassian API token inherits the permissions of the user it belongs to, so the account must have access to the projects you want Cymph to write into.
Use a dedicated Atlassian service account rather than a personal one — issues created by Cymph will be attributed to whichever account owns the token.
What Cymph reads and writes
Cymph reads projects, issue types, and field definitions so it can build a valid issue payload, then creates issues.
Cymph never deletes issues. Nothing already in your JIRA project is removed by the integration.
Testing the connection
