Issue identity
Issue IDs, keys, summaries and issue types.
Jira Cloud connector · Project reports & issue updates
Bring the current issues in one Jira Cloud project into your reports and AI assistants. Use the same project context for supported issue changes, with provider permissions and Datapipe access kept separate.
Start free See what you can change
Updated November 2026
| Issue | Summary | Status |
|---|---|---|
| OPS-214 | Review vendor contract | In Progress |
| OPS-219 | Confirm launch checklist | To Do |
| OPS-202 | Update onboarding guide | Done |
Reports show the current accessible issues, not a reconstruction of the project on a past date.
Issue IDs, keys, summaries and issue types.
The workflow status Jira returns for each accessible issue.
Date-only due dates, created dates and updated dates.
One connected Cloud site and project. Add other projects separately.
1 reporting dataset with its own fields. Open it in the app, then choose your columns.
Current accessible issues in one Jira Cloud project, independent of report dates. Standard IDs, summary, issue type, status, date-only due date and timestamps. Search can lag recent edits. Custom fields are discovered separately for supported edits; activity, comments and historical productivity metrics are excluded.
Update selected summary, due date, priority, assignee and supported custom fields. Rich-text descriptions and environment fields are replaced with plain text, so formatting is lost.
Apply an available workflow transition or add/remove a label. Transitions needing extra fields or having ambiguous routes must be made in Jira.
Add a comment or create an issue of the connected type. Service-project internal comments stay internal; customer replies are public and can email the customer.
Allow the changes your team needs for this data source. Teammates and AI assistants use that access; they cannot grant themselves more.
Allowed changes apply right away unless you require approval. Set approval for risky changes, every change or a specific person. Changes history records who made each update and its result.
Changes the summary, due date or single-line custom text fields you allow on issues of the connected project and issue type. Every issue must have the same editable fields. Jira automation rules and notifications may react. If someone edits the issue in Jira at the same moment, the later edit wins. Status transitions, assignees, descriptions, security level, creating and deleting are not offered.
Changes the issue fields you allow in the connected project and issue type: summary, description and environment as plain text, due date, priority, assignee, and custom text, paragraph, URL, number, date, date-time and single-choice fields. Rich text is replaced with plain text, so its formatting is lost. Jira notifies watchers and automation rules may run. Multi-choice, cascading, people-picker and app fields are not offered.
Moves one issue to a status in its workflow, using the one Jira transition that leads there. Moves that ask for extra fields, or that have more than one route, are refused; make those in Jira. Workflow rules, post functions and notifications run as they would in Jira.
Adds or removes one label on one issue in the connected project. A label nobody has used yet becomes a new label in Jira. Filters and automation rules that watch labels may react.
Adds one comment as the connected Jira account. In Jira Service Management projects it's marked internal, so customers don't see it and aren't emailed. In other projects everyone who can see the issue can read it, and watchers are notified. Datapipe can't edit or delete the comment afterwards.
Adds one public comment to a Jira Service Management request. Jira emails it to the customer and everyone else on the request, and it shows in the customer portal. It can't be unsent. Only works in service projects.
Creates one issue in the connected project with the connected issue type, filling the fields you allow. Allow every field Jira requires. Rich text is sent as plain text. Jira notifies watchers and automation rules may run.
Permanently deletes one issue in the connected project, with its comments, attachments and history. Jira has no undo for this. Issues with sub-tasks are refused. The Jira account needs the Delete issues permission.
| Field | Before | After |
|---|---|---|
| Due date | 2026-11-10 | 2026-11-24 |
8 report fields across 1 datasets.
Search the available fields. Hover or tap a field to see what it means.
No fields match. Try another search or choose All.
Ask about the current issues in the connected project. Prepare a supported change only with the Jira permissions and Datapipe access required for that action.
Example
Which issues are overdue and still not done?
List issues with a past due date and an unfinished status. Review an issue before proposing a new due date, comment or workflow move.
Jira Cloud sign-in is required and is offered only when available in Data sources. Use your site address, numeric project ID and a reference issue for the issue type you want to manage. Customer API tokens are not supported.
Jira Cloud only. Reports exclude comments, activity history, custom-field values and historical velocity or productivity metrics. Search results can lag recent changes. Supported custom fields are discovered separately for editing.
Choose Jira Cloud in Data sources when it is available.
Sign in to Jira and enter the Cloud site, numeric project ID and a reference issue in that project. You do not need to register your own developer app.
Choose a report and destination. Configure allowed actions, fields, teammates and approvals separately; connecting alone enables no changes.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
No. This connector uses Jira Cloud sign-in and Cloud REST APIs.
No. Reports show current project issues and their current fields. They do not reconstruct past statuses, sprint history or historical productivity.
Yes. Initial sign-in requests reporting access. Optional changes require the provider permissions for the chosen action and separate Datapipe access. Signing in does not enable changes.
No. Wait until Jira Cloud is available in Data sources. A developer app registration alone does not make a customer connection ready.
Jira deletion needs separate provider permission and action access. It is not included with ordinary issue edits. Deletion is permanent, and issues with subtasks are refused.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
One for each Jira Cloud account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Check Jira Cloud availability in Data sources, then connect the project you want to report on.