Jira

Jira is a connector: it links a MeDo app to one Jira Cloud site, so the app can read projects, boards, sprints, issues, and comments, and can create or change issues on that site. The app works with the projects and issues the connected account can reach.

#What you can build

• A private sprint dashboard. List the open issues of one project with their status, assignee, and due date.
• A bug-report page. Turn a visitor's submission into a Jira issue in a chosen project, with the reporter's email in the description.
• A release-note tool. Pick a version, list the issues fixed in that sprint, and post the summary back as a comment on each issue.
• A triage board. Show unassigned issues and assign one to a teammate after confirming the change.

Jira fits when work is already tracked as Jira issues and the app should add a focused view or a structured way in. It is not a reporting product: issue lists are paged, see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point and only reads data.

Use @Jira to build a private sprint dashboard that only I can sign in to, listing open issues in my Scrum project with status, assignee, and due date.

Use @Jira to build a bug-report page where a visitor's submission creates a Jira issue in the backlog with the reporter's email in the description.

Use @Jira to build a release-note tool: I pick a version, it lists the issues fixed in that sprint, and I post the summary back as a Jira comment on each issue.

Use @Jira to build a triage board that shows unassigned issues and lets me assign one to a teammate after I confirm the change.

#Prepare and connect

You need a Jira Cloud site and an account that can already see the project the app should use. No API token or Atlassian app registration is involved.

1. Open Skills & Connectors in the sidebar and search for Jira.
2. Open the Jira card and click Connect.
3. Enter your site's subdomain — the part before .atlassian.net, for example acme for acme.atlassian.net.
4. Sign in to Atlassian and approve the access MeDo asks for.
5. The button changes to Connected.

If you start building before connecting, MeDo shows a Jira connection button under its reply. You can connect there instead.

If your Atlassian account can reach several sites, check the site the app uses after connecting: ask the app to list the sites the connection sees, and reconnect with the right subdomain if it picked the wrong one.

#Use it in your app

• The app uses your connected site, not each visitor's own Atlassian login. Visitors do not need a Jira account. Keep internal issue views behind your app's own sign-in and limited to the intended people.
• Choose the project in the prompt, or let the app offer a picker. Either way the app should work against a project you chose, not against whatever a visitor selects.
• Issue lists are pages, not totals. Each page holds 50 issues. Ask the app to show a page with a clear way to load more, and avoid presenting one page as the whole backlog.
• Issue types and statuses are resolved by ID. A site in another language shows its own type and status names, so the app picks them from the site's lists instead of using fixed English names.
• Status changes follow the project's workflow. The app offers only the transitions that are available for the issue right now, and uses the transition's ID.
• Assignment uses the account ID. Display names and emails are only a fallback, because a site can hide member emails.
• Writes are confirmed first. MeDo previews the new issue, or the exact field and new value, before saving. This covers creating and editing an issue, moving it through a transition, assigning it, commenting, and linking two issues.
• Comments and descriptions accept Markdown. The app converts Markdown to Jira's document format.
• Internal notes belong to the app. Notes and follow-up state that Jira has no field for live in your app's tables, keyed to the real issue.

#Limits and troubleshooting

"Connection required" appears in the app. Ask the app owner to open the connector card and click Connect, then reload.

A new issue is rejected for its type. On a localised site, send the type by its numeric ID from the site's type list instead of an English name such as "Task".

Assignment looks like it did nothing. A successful assignment returns an empty response. Read the issue back to confirm the assignee.

A transition is rejected. The workflow of that issue does not offer it right now. List the issue's available transitions and use one of their IDs.

An issue was not updated. Writes do not retry automatically. Open the issue in Jira, confirm what actually happened, and only then repeat the change.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing access & roles — restrict who can read and change connected data.