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.
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.
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.
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.
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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (39 steps)
organization_value
trim
Trim whitespace from setting organization
project_value
trim
Trim whitespace from setting project
comment_text_value
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting azure devops has data
has_organization
compare
Check if organization value has data
has_project
compare
Check if project value has data
has_work_item_id
compare
Check if setting work item id does not equal 0
has_comment_text
compare
Check if comment text value has data
skip_work_item_read
any
Check if any of the conditions are true
work_item
?
skip: step.skip_work_item_read equal true
live_work_item_id
default
Apply default
work_item_state
default
Apply default
has_work_item_state
compare
Check if work item state has data
work_item_state_norm
lowercase
Convert work item state to lowercase
work_item_already_terminal
compare
Check if work item state norm is one of setting terminal states
skip_comment_context
any
Check if any of the conditions are true
comments_raw
?
skip: step.skip_comment_context equal true
existing_comments
default
Apply default
comment_count_before_create
count
Count items in existing comments
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment id has data
created_at
date_add
Add 0 days to
raw_work_item_key
join
Join items with ":"
work_item_key_colon
replace
Replace text in raw work item key
work_item_key_slash
replace
Replace text in work item key colon
work_item_key_dot
replace
Replace text in work item key slash
work_item_key_at
replace
Replace text in work item key dot
work_item_key_space
replace
Replace text in work item key at
work_item_key_left_angle
replace
Replace text in work item key space
work_item_key_right_angle
replace
Replace text in work item key left angle
work_item_key_plus
replace
Replace text in work item key right angle
work_item_key_equals
replace
Replace text in work item key plus
work_item_key_question
replace
Replace text in work item key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_azure_devops_work_item_comment_closure_watch
?
skip: step.skip_closure_seed equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
format
setting
=
markdown
project
setting
=
azure devops
setting
=
comment text
setting
=
organization
setting
=
work item id
setting
=
0
terminal states
setting
=
done,closed,removed,completed
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.