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 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.
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.
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.
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.
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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
active_rows
?
timed_out_rows
?
closed_rows
?
▼
Process (10 steps)
close_key
trim
Trim whitespace from setting close key
close_is_timed_out
starts_with
Check if close key starts with data.shared.recipe.recued-core_azure-devops-work-item-comment-closure.timed_out.
close_is_closed
starts_with
Check if close key starts with data.shared.recipe.recued-core_azure-devops-work-item-comment-closure.closed.
close_allowed
any
Check if any of the conditions are true
close_terminal_row
?
skip: step.close_allowed not_equal true
lifecycle_rows
flatten
Flatten nested lists in
shown_rows
slice
Take a subset of
row_count
count
Count items in lifecycle rows
table
to_table
Format results as a data table
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
close key
setting
=
row limit
setting
=
50
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.