Use “Comment on GitLab issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Comment on GitLab issue with closure watch
Use “Comment on GitLab issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
GitLab Issue Note Closure Loop
4 pinned recipes
Use GitLab Issue Note Closure Loop in Recued for issues, notes, comments, and developer workflow. It includes 2 ready-to-run workflows and 1 related pack in one install.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “GitLab issue note closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.
Use “GitLab issue note closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Use “GitLab issue note closure watcher lifecycle review” in Recued. It carries out the named workflow using the connections and settings you choose.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (35 steps)
project_id_value
trim
Trim whitespace from setting project id
issue_iid_value
trim
Trim whitespace from setting issue iid
note_body_value
trim
Trim whitespace from setting note body
has_connection
compare
Check if setting gitlab has data
has_project_id
compare
Check if project id value has data
has_issue_iid
compare
Check if issue iid value has data
has_note_body
compare
Check if note body value has data
skip_issue_read
any
Check if any of the conditions are true
issue
?
skip: step.skip_issue_read equal true
notes_raw
?
skip: step.skip_issue_read equal true
state
default
Apply default
has_issue_state
compare
Check if state has data
issue_already_closed
compare
Check if state equals closed
notes
default
Apply default
note_count_before_create
count
Count items in notes
skip_note_create
any
Check if any of the conditions are true
created_note
?
skip: step.skip_note_create equal true
created_note_id
default
Apply default
has_created_note
compare
Check if created note id has data
created_at
date_add
Add 0 days to
raw_issue_key
join
Join items with ":"
issue_key_colon
replace
Replace text in raw issue key
issue_key_slash
replace
Replace text in issue key colon
issue_key_dot
replace
Replace text in issue key slash
issue_key_at
replace
Replace text in issue key dot
issue_key_space
replace
Replace text in issue key at
issue_key_left_angle
replace
Replace text in issue key space
issue_key_right_angle
replace
Replace text in issue key left angle
issue_key_plus
replace
Replace text in issue key right angle
issue_key_equals
replace
Replace text in issue key plus
issue_key_question
replace
Replace text in issue 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_gitlab_issue_note_closure_watch
?
skip: step.skip_closure_seed equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
gitlab
setting
=
issue iid
setting
=
note body
setting
=
project id
setting
=
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.