Write

Hand over a Jira issue with a clear note

For project managers moving work between people who want the right assignee and a handover comment, by asking their AI assistant.

Triage and assign a Jira issue

Reassign WEB-1042 to Sam Patel, Jordan is out next week.

WEB-1042 is currently assigned to Jordan Lee and In progress. - New assignee: Sam Patel, one active match - Comment: Handing over to Sam Patel, Jordan is out next week Jordan is mid-task on this issue. Shall I reassign it?

Jira

Sample figures. Your results come from your own account.

jira-get-issue

jira-get-issue-watcher

jira-get-user

jira-assign-issue

jira-add-issue-comment

On this page

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Jira

Run it on your own Jira data.

Connect Jira, pick your AI tool and paste the prompt.

The problem

Reassigned issues arrive with no context

Handing a Jira issue to someone else means checking who has it now, finding the right person among similar names and leaving a note saying why. Skip the note and the new owner has no context; skip the check and you take work mid-task.

Without PopdockAI

Check who has the issue now
Pick the new assignee from similar names
Write a handover comment
Take work off someone mid task by mistake

With PopdockAI

The issue is read and you are asked before taking it off someone
The assignee must match exactly one active person
You see current and new owner and the comment first
It assigns once, comments only if that worked, and reads it back

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt

**Objective:** Assign the Jira issue `{issue-key}` to `{assignee}` and leave a comment recording the handover and the reason `{reason}`.

**Step 1: Read the issue first**

Call `jira-get-issue` with issue-key set to {issue-key}. If it returns nothing, stop. Note the current assignee and status. If it is already assigned to someone other than {assignee}, say who and ask whether to take it off them before going further.

**Step 2: Resolve the numeric issue id**

Both write tools need the numeric issue-id, which `jira-get-issue` does not return. Call `jira-get-issue-watcher` with issue-key set to {issue-key} and read issue-id. If it returns no rows, the id cannot be resolved, report that and stop rather than guessing.

**Step 3: Resolve the assignee**

Call `jira-get-user` with name.contains set to {assignee}, or email if it looks like an address. Take user-account-id. If more than one person matches, list them and stop. If the account is not active, stop and say so.

**Step 4: Confirm**

Show the issue key, its current assignee, the new assignee with their email, and the comment you intend to leave. Ask for confirmation. Do not proceed without it.

**Step 5: Write, in this order**

1. `jira-assign-issue` with id set to the issue id from Step 2 and account-id from Step 3. Once.
2. `jira-add-issue-comment` with issue-id set to the same id and body set to the handover note, which states who it moved to and the reason {reason}. Once.

If the assign call fails, do NOT leave the comment.

**Step 6: Confirm**

Call `jira-get-issue` with issue-key set to {issue-key} and report the assignee now on it.

**Rules & Guidelines:**

* Only `jira-assign-issue` and `jira-add-issue-comment` may be called, once each, after the Step 4 confirmation.
* Do NOT call `jira-update-issue`, this prompt does not change status, summary or dates.
* Do NOT add the new assignee as a watcher or a voter unless the user asks.

**Validation:**

* If {assignee} is ambiguous or unknown, stop at Step 3 and ask.
* If {reason} is empty, write the comment as a plain handover note without inventing a justification.

Who it's for

One answer, three teams that use it

Project managers

Rebalance work with context

Move an issue to someone else with a handover note, so they can start straight away.

Reassign API-219 to Priya Shah, Tom is moving to the mobile team.

Team leads

Cover for someone who is away

Hand issues over before a holiday, with a check that you are not taking active work by surprise.

Give MOB-88 to Dana Whitfield while Sam is on leave next week.

Developers

Pass on an issue cleanly

Hand an issue to a teammate with a comment explaining why, in one request.

Assign WEB-1107 to Tom Reyes, he knows the payment code better.

How it works

What PopdockAI does when you ask

You name the issue, new assignee and reason, and your AI assistant checks the current owner. Nothing changes until you have seen the handover and said yes.

Ask

You name the issue, the new assignee and a reason.

Your AI tool

Check

It reads the issue and asks before taking it off someone else.

jira-get-issue

jira-get-user

Confirm

You see current and new owner and the handover comment, and say yes.

No items found.

Assign

It assigns once, comments only if that worked, and reads the assignee back.

Your AI tool

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.

get-data

jira-get-issue

Returns Jira issues with their project, issue type, status, assignee, reporter, dates and estimates. Filter by project, status, assignee or date range to pull a backlog, a sprint or one person's open work.

get-data

jira-get-issue-watcher

Returns the users watching Jira issues, with the issue and project they are watching, so you can see who is following a piece of work.

get-data

jira-get-user

Returns Jira users with their display name, email address and active status. Use it to resolve a person's name to the account id an assignment needs.

run-action

jira-assign-issue

Assigns a Jira issue to a user. Pair it with the Jira users tool to turn a person's name into the account id it expects.

run-action

jira-add-issue-comment

Adds a comment to a Jira issue, which is the usual way to record why something was reprioritised, reassigned or closed.

Read only.Nothing in Jira Changes

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

Work changes hands with a clear note

Related use cases

More ways to put this data to work

Close out Jira bugs for passing Ghost Inspector tests

Ask your AI to find Jira bugs whose Ghost Inspector tests pass consistently and it lists close-out candidates with evidence, posting comments only if you ask.

Learn More

File a Jira bug for a Ghost Inspector test failure

Ask your AI to file a Jira bug for a Ghost Inspector failure and it gathers the failing step and console errors, checks for duplicates, and links both ways after you confirm.

Learn More

Verify a Jira fix by rerunning its Ghost Inspector test

Ask your AI to verify a Jira fix and it finds the Ghost Inspector test behind the bug, runs it once and posts one verification comment.

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.