Agency account managers
Send each client a status report from their own project, on a schedule.
Report on current project issues and make field edits, status moves, labels, comments, customer replies, new issues and deletions in the project and issue type selected by the owner.
Updated November 2026
| Issue key | Summary | Due date |
|---|---|---|
| 1,240 | Review delivery plan | Oct 27 |
| 640 | 640 | Oct 28 |
| 210 | 210 | Oct 29 |
Send each client a status report from their own project, on a schedule.
See overdue issues by type and status without exporting CSVs.
Get a weekly answer to "what moved, what slipped" in a sheet or in ChatGPT.
Read accessible current issue identifiers, summaries, statuses, issue types, due dates and timestamps.
Changes stay off until you allow them. Allowed changes apply to Jira Cloud right away, and history keeps the values before and after.
Search results can lag recent edits.
Refresh current issues from the selected project.
Limit: Bring summaries, statuses and due dates into the delivery review.
Set a clearer summary on an existing issue in the connected project and issue type.
Limit: Jira must still allow that field to be edited on that issue.
See the problem in your report, then make the fix in Datapipe instead of opening Jira Cloud, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to Jira Cloud.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayOpen each Jira issue, edit the due date, and repeat for the whole sprint.
With DatapipeYour Jira report lists issues due this week. Set new due dates from Datapipe. Status and assignee stay as they are.
TodayRewrite summaries like "fix" or "see Slack" one ticket at a time.
With DatapipeFilter the report for short or vague summaries. A teammate or ChatGPT writes clear wording, and each change is recorded.
TodayLook up the reference and paste it into each issue by hand.
With DatapipeFill in a single-line custom text field, if that field is allowed. Descriptions and workflow status are not changed.
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.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
TodayOpen each issue after the meeting and change the priority by hand.
With DatapipeYour Jira report lists the issues you discussed. Set the new priority for each. Only allowed fields can change.
TodayLook up the value and paste it into each issue's custom field.
With DatapipeFill in an allowed custom text, number or choice field. Jira checks the field is still editable on that issue.
TodayOpen each issue and pick a new assignee from Jira's list.
With DatapipePick the new assignee from the people Jira lets you assign in the project.
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.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
TodayDrag each issue across the board after the release goes out.
With DatapipeThe report lists issues still in review. Move each to Done from Datapipe. Jira runs its usual workflow rules.
TodayFind blocked issues and move them back through the workflow one by one.
With DatapipeSet the earlier status. If the move needs extra fields or has two routes, Datapipe tells you to make it in Jira.
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.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
TodayOpen each issue and type the label, hoping you spell it the same way every time.
With DatapipeAdd the label to each issue from the report. The label is added exactly as written.
TodaySearch for the label and delete it from each issue by hand.
With DatapipeThe report lists issues with the label. Remove it from each from Datapipe.
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.
Supported fields: Label (no spaces), Change.
TodaySwitch to the internal note tab in Jira Service Management and type carefully so you don't reply to the customer.
With DatapipeAdd the note from Datapipe. In service projects it's always marked internal, so the customer isn't emailed.
TodayCopy the decision from Slack into the issue comments.
With DatapipeA teammate or Claude drafts the comment and adds it. Watchers get Jira's usual notice.
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.
Supported fields: Comment (plain text).
TodayOpen the request, write the reply and send it from the agent view.
With DatapipeA teammate drafts the reply from the report. Jira emails the customer as soon as it's added, so you can set customer replies to need approval first.
TodayPaste your saved answer into each request that asks it.
With DatapipePost the answer from Datapipe. Datapipe only offers customer replies in service projects.
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.
Supported fields: Reply to the customer (plain text).
TodayCreate each issue in Jira and retype the notes.
With DatapipeClaude drafts the summary and fields per action item, and Jira creates each one in the connected project.
TodayOpen Jira, pick the project and issue type, then copy the details in.
With DatapipeA teammate fills in the summary, description and priority, and Jira creates the issue. Fields Jira requires must be filled first.
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.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
TodayFind each duplicate, open the menu and delete it, hoping you picked the right one.
With DatapipeDelete the duplicate after checking the issue key and summary. Jira deletes it permanently, and the notice says so.
TodaySearch for the test issues and delete them one at a time.
With DatapipeThe report lists issues created during the demo. Delete each from Datapipe. Issues with sub-tasks are refused.
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.
Supported fields: Delete.
| Field | Before | After |
|---|---|---|
| Due date | 2026-11-10 | 2026-11-24 |
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider permissions still apply, and automations in Jira Cloud may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
A Jira Cloud login with access to the account you want to report on.
Read access for reports. The 8 change actions need edit access in Jira Cloud and stay off until the owner, an admin or a project manager allows them.
Standard IDs, summary, issue type, status, date-only due date and timestamps. Custom fields are discovered separately for supported edits; activity, comments and historical productivity metrics are excluded.
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.
Updates owner-selected summary, date-only due date and supported single-line custom text fields in the connected project and issue type. Each issue must expose the same editable field context. Jira rules and notifications may react; external edits can race execution. No workflow transitions, assignment, descriptions, security changes, creation or deletion. The owner, an admin or a project manager controls field grants and who can make changes. Every change is recorded in history.
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.
8 report fields across 1 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Jira Cloud changes. They can never widen their own access.
Which issues in Jira Cloud are past their due date and not yet done?
Seven issues are past due: 3 bugs and 4 stories. The oldest is 12 days late and still In Progress.
Create a project and choose this source in Data sources.
Pick where it goes. This one sends the numbers to CSV.
Pick where it goes. Choose a report and destination, then configure optional writable fields and teammates separately.
| Issue ID | Issue key | Summary | Due date | Issue type | Status | Created at | Updated at |
|---|---|---|---|---|---|---|---|
| 1024 | 1,240 | Review delivery plan | Oct 27 | 1,240 | In progress | 1,240 | Oct 27 |
| 1025 | 640 | 640 | Oct 28 | 640 | Pending | 640 | Oct 28 |
| 1031 | 210 | 210 | Oct 29 | 210 | Refunded | 210 | Oct 29 |
Sample numbers, so you can see the shape. Your report uses your accounts.
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.
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.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
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.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Jira Cloud account. Nobody else gets a Jira Cloud login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
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.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Jira Cloud received it, the request is marked Uncertain and is never retried automatically, so you can check Jira Cloud first.
Yes. Datapipe reads the reports on this page and can make 8 kinds of change: update approved issue fields; update any supported issue field; move an issue to another status; add or remove an issue label; add an internal comment; reply to the customer on a service request; create an issue; delete an issue. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 8 report fields across 1 datasets. You pick the columns when you build the report.
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. Account permissions and the records available from the provider determine which rows can be read.
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.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Jira Cloud when you are ready.