/
/
See the Jira work behind every ServiceNow P1
For IT and service desk leads who want the development backlog behind priority 1 incidents and problems, by asking their AI assistant.
On this page
Connector
Connect Jira, pick your AI tool and paste the prompt.
The problem
The service desk cannot see the dev work behind a P1
Priority 1 incidents and problems in ServiceNow depend on fixes tracked in Jira, but the service desk cannot see whether that work is assigned, on schedule or raised. Answering it means looking up each P1 by hand.
Without PopdockAI
- List open P1 incidents and problems
- Search Jira for each record number
- Check status, owner and due date
- Add up open story points by hand
With PopdockAI
- Open P1 incidents and problems are read from ServiceNow
- Jira issues carrying each record number are found
- Overdue and unassigned issues are flagged
- P1s with no Jira issue are listed apart, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Show the Jira development backlog behind open priority 1 ServiceNow incidents and problems opened in the last `{lookback-days}` days (default 30), optionally limited to Jira project `{project-key}`. Read only.
**Step 1: Collect the open P1s in ServiceNow**
Call `servicenow-get-incident` with `priority` set to 1 and `opened.from` set to `{lookback-days}` days ago (default 30). Call `servicenow-get-problem` with the same `priority` and `opened.from`. Keep only records that are not Resolved, Closed or Canceled. If the priority filter returns nothing, retry once with the value as ServiceNow displays it (for example "1 - Critical").
**Step 2: Find the Jira work for each**
The link between the two systems is the ServiceNow number in the Jira summary, written as `[INC0010023]`. For each record, call `jira-get-issue` with `summary.contains` set to its number, filtered by `project-key` when `{project-key}` is given. A record with no match has no dev issue.
**Step 3: Report**
* **P1s with dev work:** ServiceNow number, short description, opened date, assignment group; Jira key, status, assignee, due date, story points. Flag issues past their due date and issues with no assignee.
* **P1s with no Jira issue:** number, short description, opened date, assignment group. Suggest the `escalate-to-jira` prompt for these.
* **Totals:** open P1 count, how many have dev work, how many Jira issues are unassigned or overdue, and the sum of story points still open.
**Rules & Guidelines:**
* `servicenow-get-incident` and `servicenow-get-problem` are on the servicenow server. `jira-get-issue` is on the jira server.
* This prompt is read only. Do not call `jira-add-issue`, `jira-update-issue`, `jira-assign-issue`, `servicenow-update-incident` or `servicenow-update-problem`.
**Validation:**
* If there are no open P1 records in the window, say so and stop.
* If a Jira issue has no story points or due date, show the field as blank rather than zero.
* If one ServiceNow record matches several Jira issues, list them all under that record.Who it's for
One answer, three teams that use it
Major incident managers
Bring the dev picture to the review
See the Jira work behind each P1 with status and points, ready for the incident review.
What Jira work sits behind open ServiceNow P1s from the last 14 days?
Problem managers
Catch P1s with no fix in progress
P1s with no Jira issue at all are listed, so none go without development work.
Which open P1 problems in ServiceNow have no Jira issue?
Engineering managers
Prioritise P1 work
See overdue and unassigned issues behind P1s in your project, with story points still open.
Show Jira issues in OPS behind open ServiceNow P1s that are overdue or unassigned.
How it works
What PopdockAI does when you ask
You give a lookback period and your AI assistant matches every open ServiceNow P1 to its Jira work. You get the backlog per P1 and totals, and nothing is changed.
01
Ask
You give a lookback period and optionally a Jira project.
02
Read
It reads open priority 1 incidents and problems in ServiceNow.
03
Find
It finds the Jira issues carrying each record number.
04
Report
You get the work per P1, overdue and unassigned flags and P1s with no issue.
What PopdockAI provides
The tools behind the answer
Ready made tools for Jira and one secure connection to your AI tool. No code, no exports.
servicenow-get-incident
servicenow-get-problem
jira-get-issue
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
The real dev backlog behind every P1
Related use cases
More ways to put this data to work
Sync Jira progress to a ServiceNow record
Ask your AI to sync Jira progress to a ServiceNow record and it summarises the linked issue in a work note and adds it once after you confirm.
Learn More
Find stale Jira issues linked to ServiceNow
Ask your AI to find stale Jira issues linked to ServiceNow and it flags stalled pairs and records finished on one side but open on the other.
Learn More
Audit stale Jira issues
Ask your AI to audit stale Jira issues and it sorts open work into untouched, unassigned, past due and unestimated groups, then names the one action that clears most.
Learn More
Backfill Jira issues for untracked errors
Ask your AI to backfill Jira issues for untracked Bugsnag errors and it drops errors already tracked, then creates and links capped issues after you approve.
Learn More
Check the Jira status of a Zendesk escalation
Ask your AI for the Jira status of a Zendesk escalation and it reads the linked issues, flags disagreements and drafts a plain-language reply for you only.
Learn More
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.