Connectors

/

BugHerd

/

Close BugHerd bugs for completed Todoist tasks
Write
Cross-Connector

Close the BugHerd bugs whose Todoist task is done

For developers who want BugHerd bugs closed when the linked Todoist task is finished, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Close BugHerd bugs for completed Todoist tasks
Close the BugHerd bugs for anything I completed in my Todoist project Web Fixes this week. The BugHerd project is Contoso Storefront.
Three completed Todoist tasks in Web Fixes reference bugs in Contoso Storefront, and all three are still open. - Bug 212, Checkout button misaligned, task completed Nov 3 - Bug 218, Login timeout on mobile, task completed Nov 4 - Bug 220, Wrong tax label, task completed Nov 4 - Bug 205 is already closed, so I skipped it Shall I set these three bugs to closed?
BugHerd
Sample figures. Your results come from your own account.
todoist-get-projects
todoist-get-tasks
bugherd-get-projects
bugherd-get-tasks
bugherd-get-columns
bugherd-update-task

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

BugHerd

BugHerd
Run it on your own BugHerd data.

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

Try PopdockAI free

The problem

Finished work leaves bugs open

Completing a Todoist task does nothing to the BugHerd bug behind it. Closing them by hand means comparing both boards and editing each bug one at a time.

Without PopdockAI

  • List the tasks you completed in Todoist
  • Find the bug number in each task
  • Open each bug in BugHerd
  • Change the status one bug at a time

With PopdockAI

  • Completed tasks are read and bug numbers taken from the task text
  • Each bug is checked in BugHerd, skipping ones already closed
  • You review a table and confirm before any status changes
  • Only the status is set, and Todoist is never touched

The prompt

Use this prompt

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

Prompt
**Objective:** For Todoist tasks in project `{todoist-project}` completed in the last `{days}` days (default 7) that reference a bug in BugHerd project `{bugherd-project}`, set the bug to status `{closed-status}` (default: closed) after confirmation.

**Step 1: Read completed Todoist tasks**

Call `todoist-get-projects` (Todoist server) with `name.contains` set to `{todoist-project}`; stop on zero or multiple matches. Call `todoist-get-tasks` with that `project-id` and `is-completed` true. Keep tasks whose `completed-at` falls within the window. Extract bug numbers (#123 style) from `content` and `description`; ignore tasks without one.

**Step 2: Check the bugs in BugHerd**

Call `bugherd-get-projects` (BugHerd server) with `name.contains` set to `{bugherd-project}`; stop on zero or multiple matches. For each number call `bugherd-get-tasks` with `project-id` and `task-number`. Skip bugs that are already in the target status, and report numbers that are not found.

**Step 3: Confirm**

Show a table: bug number, title, current status, Todoist task content, completed-at. Ask the user to confirm and write nothing until they say yes. They may drop rows. Use `bugherd-get-columns` with the `project-id` to check the target status name exists, and stop if it does not.

**Step 4: Update**

For each confirmed bug call `bugherd-update-task` (BugHerd server) with `project-id`, `task-id` and `status` set to `{closed-status}`.

**Step 5: Report**

Bugs updated, bugs skipped with the reason, and any failures.

**Rules & Guidelines:**

* The Todoist tools are on the Todoist server; the BugHerd tools are on the BugHerd server.
* The only write allowed is `bugherd-update-task`, only the `status` field, and only after the confirmation in Step 3. Never call `bugherd-add-comment`, `bugherd-move-task`, or any Todoist write tool.

**Validation:**

* If no completed task carries a bug reference, report that and stop.
* Never change a bug whose number was matched only by guesswork; the number must appear in the task text.

Who it's for

One answer, three teams that use it

Developers

Close bugs without a second pass

Mark a bug closed once the task is done, instead of switching to BugHerd to repeat the update.

Close the BugHerd bugs for tasks I finished in my Todoist project Sprint Fixes in the last 3 days. BugHerd project is Fabrikam Portal.

QA leads

Keep the bug board accurate

Review the completed tasks and the bugs they point to in one table, and confirm only the ones that are truly fixed.

Which BugHerd bugs in Northwind Traders Web still show open even though their Todoist task is complete?

Project managers

Report on real bug counts

A bug board that matches finished work means the open bug count you report is not padded with fixed items.

Close the fixed bugs for Todoist project Release 4.2 completed in 14 days, set them to the Done status in BugHerd project Contoso App.

How it works

What PopdockAI does when you ask

You name both projects and your AI assistant matches completed tasks to bugs. Nothing is written until you confirm the list, and a bug is only touched if its number is in the task text.

Ask

You name the Todoist project, the BugHerd project and the time window.

Your AI tool

Match

It reads recently completed tasks, takes bug numbers from the task text and checks each bug in BugHerd.

todoist-get-projects
todoist-get-tasks
bugherd-get-projects
bugherd-get-tasks
bugherd-get-columns

Confirm

You see the table of bugs and tasks, drop any rows and say yes.

No items found.

Update

It checks the status exists, sets it on the confirmed bugs and reports the results.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for BugHerd and one secure connection to your AI tool. No code, no exports.

get-data

todoist-get-projects

Returns projects from Todoist.
get-data

todoist-get-tasks

Returns tasks from Todoist.
get-data

bugherd-get-projects

Returns BugHerd projects with their website, owner, visibility and status. Filter by project ID, name, owner or active status.
get-data

bugherd-get-tasks

Returns tasks from BugHerd projects: title, description, status, severity, assignee, requester, page, tags, due date and external ID. Filter by project, task number, title, status, severity, assignee, requester email, external ID and due or created date.
get-data

bugherd-get-columns

Returns the columns of BugHerd task boards and how many tasks each holds. Filter by project or column name.
run-action

bugherd-update-task

Changes a BugHerd task severity, status (board column) or assignee, recording who made the change.
Read only.Nothing in BugHerd 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.

How Popdock AI secures your data

The outcome

Bug status that matches the work

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

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.

Try PopdockAI Free
See Documentation