Name: Azure DevOps work item comment closure watcher
Author: recued-core

Azure DevOps work item comment closure watcher

by recued-core v1

Scheduled adopter for Azure DevOps work item comment closure rows seeded by comment-azure-devops-work-item-with-closure. It lists only Recued-originated work-item-comment watches, re-reads a bounded batch of Azure DevOps work item, and closes the shared row when Azure DevOps reports a configured terminal state such as done, closed, removed, or completed. It can notify the owner on closure, but it never creates, updates, assigns, transitions, links, attaches to, deletes, comments on, or otherwise mutates Azure DevOps work items.

Complete workflow

Azure DevOps Work Item Comment Closure Loop 4 pinned recipes

Workflow pack for Recued-created Azure DevOps work item comments. It composes the Azure DevOps capability pack with a closure ledger: add one owner-approved comment to an existing work item, persist only the connection/organization/project/work-item/comment linkage in data.shared, and let a scheduled watcher re-read that exact work item until Azure DevOps reports a configured terminal state such as done, closed, removed, or completed. This pack does not replace Azure DevOps work item comments, native notifications, state transitions, assignments, boards, queries, service hooks, or general work-item reporting; it adds Recued-visible closure state for work item comments Recued created.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Azure DevOps work item comment closure watcher

This recipe Background automation

azure-devopswork-itemscommentsdeveloper-workflow

by recued-core pinned v1

Comment on Azure DevOps work item with closure watch

Workflow origin for the Azure DevOps work item comment closure loop. It reads one Azure DevOps work item and current comments for context, creates exactly one owner-provided comment through recued-core.azure-devops.work_item.comment.add, and when the comment succeeds it seeds durable data.shared closure state for azure-devops-work-item-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, assign, transition, link, attach to, delete, or otherwise mutate Azure DevOps work items.

azure-devopswork-itemscommentsdeveloper-workflow

by recued-core pinned v1

Azure DevOps work item comment closure watcher timeout

Background automation

Low-frequency timeout role for recued-core/azure-devops-work-item-comment-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

azure-devopswatchertimeoutowner-review

by recued-core pinned v1

Azure DevOps work item comment closure watcher lifecycle review

Owner-visible list/close role for recued-core/azure-devops-work-item-comment-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

azure-devopswatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 88 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch

▼ shared_work_item_watches ?

▼

Process (87 steps)

■ now date_add

Add 0 days to

■ watch_rows filter

Filter by condition

■ watch_rows_for_connection filter

Filter by condition

■ watch_rows_with_organization filter

Filter by condition

■ watch_rows_with_project filter

Filter by condition

■ watch_rows_with_work_item filter

Filter by condition

■ never_checked_watch_rows filter

Filter by condition

■ checked_watch_rows filter

Filter by condition

■ checked_watch_rows_oldest_first sort

Sort by value.last_checked_at

■ fair_watch_rows flatten

Flatten nested lists in

■ candidate_rows slice

Take a subset of

■ batch_count count

Count items in candidate rows

■ candidate_count count

Count items in watch rows with work item

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting azure devops has data

■ skip_work_item_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ work_item ?

skip: step.skip_work_item_read equal true

■ work_item_live_batch_context pick

Keep only specific fields from

■ work_item_batch_context_envelopes merge

Combine objects together

■ work_item_batch_contexts map

Extract from each item

■ live_work_item_id default

Apply default

■ live_work_item_id_live_batch_context pick

Keep only specific fields from

■ live_work_item_id_batch_context_envelopes merge

Combine objects together

■ live_work_item_id_batch_contexts map

Extract from each item

■ work_item_state default

Apply default

■ work_item_state_live_batch_context pick

Keep only specific fields from

■ work_item_state_batch_context_envelopes merge

Combine objects together

■ work_item_state_batch_contexts map

Extract from each item

■ has_work_item_state compare

Check if item work item state has data

■ has_work_item_state_live_batch_context pick

Keep only specific fields from

■ has_work_item_state_batch_context_envelopes merge

Combine objects together

■ has_work_item_state_batch_contexts map

Extract from each item

■ work_item_state_norm lowercase

Convert item work item state to lowercase

■ work_item_state_norm_live_batch_context pick

Keep only specific fields from

■ work_item_state_norm_batch_context_envelopes merge

Combine objects together

■ work_item_state_norm_batch_contexts map

Extract from each item

■ work_item_terminal compare

Check if item work item state norm is one of setting terminal states

■ work_item_terminal_live_batch_context pick

Keep only specific fields from

■ work_item_terminal_batch_context_envelopes merge

Combine objects together

■ work_item_terminal_batch_contexts map

Extract from each item

■ changed_date default

Apply default

■ changed_date_live_batch_context pick

Keep only specific fields from

■ changed_date_batch_context_envelopes merge

Combine objects together

■ changed_date_batch_contexts map

Extract from each item

■ skip_close any

Check if any of the conditions are true

■ skip_close_live_batch_context pick

Keep only specific fields from

■ skip_close_batch_context_envelopes merge

Combine objects together

■ skip_close_batch_contexts map

Extract from each item

■ closed_watch_key replace

Replace text in item watch key

■ closed_watch_key_live_batch_context pick

Keep only specific fields from

■ closed_watch_key_batch_context_envelopes merge

Combine objects together

■ closed_watch_key_batch_contexts map

Extract from each item

■ close_watch ?

skip: item.skip_close equal true

■ close_watch_live_batch_context pick

Keep only specific fields from

■ close_watch_batch_context_envelopes merge

Combine objects together

■ close_watch_batch_contexts map

Extract from each item

■ delete_closed_active_watch ?

skip: item.close_watch.ok not_equal true

■ delete_closed_active_watch_live_batch_context pick

Keep only specific fields from

■ delete_closed_active_watch_batch_context_envelopes merge

Combine objects together

■ delete_closed_active_watch_batch_contexts map

Extract from each item

■ notify_enabled compare

Check if setting notify when terminal equals true

■ notify_enabled_live_batch_context pick

Keep only specific fields from

■ notify_enabled_batch_context_envelopes merge

Combine objects together

■ notify_enabled_batch_contexts map

Extract from each item

■ should_notify all

Check if all conditions are true

■ should_notify_live_batch_context pick

Keep only specific fields from

■ should_notify_batch_context_envelopes merge

Combine objects together

■ should_notify_batch_contexts map

Extract from each item

■ notify_owner ?

skip: item.should_notify not_equal true

■ notify_owner_live_batch_context pick

Keep only specific fields from

■ notify_owner_batch_context_envelopes merge

Combine objects together

■ notify_owner_batch_contexts map

Extract from each item

■ refreshed_watch_value merge

Combine objects together

skip: item.delete_closed_active_watch.ok equal true

■ refreshed_watch_value_live_batch_context pick

Keep only specific fields from

■ refreshed_watch_value_batch_context_envelopes merge

Combine objects together

■ refreshed_watch_value_batch_contexts map

Extract from each item

■ refresh_active_watch ?

skip: item.delete_closed_active_watch.ok equal true

■ refresh_active_watch_live_batch_context pick

Keep only specific fields from

■ refresh_active_watch_batch_context_envelopes merge

Combine objects together

■ refresh_active_watch_batch_contexts map

Extract from each item

■ closed_batch_rows filter

Filter by condition

■ refreshed_batch_rows filter

Filter by condition

■ closed_batch_count count

Count items in closed batch rows

■ refreshed_batch_count count

Count items in refreshed batch rows

■ summary to_summary

Format results as a summary card

Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app

batch limit setting = 5

azure devops setting =

terminal states setting = done,closed,removed,completed

notify when terminal setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Send notificationsRead your Azure_devops connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

recued-core

Details

88 steps 5 configurable settings recipe_id: azure-devops-work-item-comment-closure-watcher

Azure DevOps work item comment closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details