Jira

Connect an Atlassian Jira Cloud site to track and automate project work. metamorphOS opens, edits, searches, and moves issues through your workflow, adds comments and assigns people, and Jira notifies metamorphOS whenever an issue or comment changes so you can trigger a process in response.

What you can do

Issues: create, look up, update, delete, and search issues with JQL (Jira Query Language).
Workflow: see the status transitions available on an issue and move it to a new status.
Collaboration: add a comment to an issue, and assign an issue to a user.
Projects and account: list the projects you can see, and look up the connected account’s details.
Issue and comment events: trigger a process automatically when an issue is created, when an issue is updated, or when a comment is added.

Before you start

You need an Atlassian Jira Cloud site and permission to create an app in the Atlassian Developer console. To receive events, you also need Jira admin access so you can register a webhook.

Set up Jira

Create an app. Go to the Atlassian Developer console, choose Create -> OAuth 2.0 integration, give it a name (for example, metamorphOS), and create it.
Set the callback URL. In the app’s Authorization settings, set the Callback URL to the value metamorphOS gives you for this connector. It must match exactly, or Atlassian rejects the sign-in.
Grant permissions. Under Permissions, add the Jira API and grant read and write access to Jira work, read access to Jira user accounts, and offline access (this keeps the connection alive without anyone signing in again). Grant nothing broader than needed, then save.
Copy the credentials. On the app’s Settings page, copy the app’s Client ID and Client secret. You will enter these in metamorphOS; never write them into the connector itself.

Connect in metamorphOS

Activate the Jira connector from the marketplace, add an account, and provide:

Client ID and Client secret: from your Atlassian app’s Settings page.
Consent: metamorphOS opens Atlassian’s sign-in page so you can grant the app access to your Jira site. After you approve, the connection stays active on its own.
Cloud ID: each account points at one Jira site, identified by its Cloud ID. Supply the Cloud ID for the site you just authorized so metamorphOS targets the right one.

Receive events (webhooks)

To trigger a process when issues or comments change, register a webhook in Jira:

In Jira, go to Settings -> System -> WebHooks and add a webhook pointing at the URL metamorphOS provides.
Enable the Issue: created, Issue: updated, and Comment: created events to feed all three triggers.
Optionally add a JQL filter (for example, project = TEST) to scope which issues fire the webhook. Leave it blank for the whole site.

Good to know

Jira does not sign its webhook deliveries, so metamorphOS cannot cryptographically verify that an event genuinely came from Jira. Keep the receiver URL private and use a JQL filter to limit what triggers your processes.
Issue descriptions and comments are handled as plain text; rich formatting is not exposed.
Field coverage is a representative subset and still expanding, so some advanced fields may not be available yet.
Not covered: attachments, worklogs, sprints and boards, custom-field schema management, and user provisioning.