Recued
Menu
← Back to recipes

Comment on Jira issue with closure watch

by recued-core v2 32 views

Use “Comment on Jira issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

Use Jira Issue Comment Closure Loop in Recued for atlassian, issues, comments, and work tracking. 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.

Jira issue comment closure watcher
Background automation

Use “Jira issue comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

jiraatlassianissuescomments
by recued-core pinned v3

Use “Jira issue comment 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.

jirawatchertimeoutowner-review
by recued-core pinned v2
View pack details, dependencies, and permissions →
How it works 37 steps

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

Process (37 steps)
■ cloud_id_value trim
Trim whitespace from setting cloud id
■ issue_id_or_key_value trim
Trim whitespace from setting issue id or key
■ comment_text_value trim
Trim whitespace from setting comment text
■ has_connection compare
Check if connections atlassian has data
■ has_cloud_id compare
Check if cloud id value has data
■ has_issue_id_or_key compare
Check if issue id or key value has data
■ has_comment_text compare
Check if comment text value has data
■ skip_issue_read any
Check if any of the conditions are true
◆ issue recued-core.jira.issue.read
Read issue on jira
skip: step.skip_issue_read equal true
■ defaults defaults
Apply defaults
■ has_issue_status_category compare
Check if status category key has data
■ status_category_key_norm lowercase
Convert status category key to lowercase
■ issue_already_done compare
Check if status category key norm equals done
■ skip_comment_context any
Check if any of the conditions are true
◆ comments_raw recued-core.jira.comment.search
Search comment on jira
skip: step.skip_comment_context equal true
■ comments default
Apply default
■ comment_count_before_create count
Count items in comments
■ skip_comment_create any
Check if any of the conditions are true
◆ created_comment recued-core.jira.comment.add
Add comment on jira
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_watch_key join
Join items with ":"
■ watch_key_colon replace
Replace text in raw watch key
■ watch_key_slash replace
Replace text in watch key colon
■ watch_key_dot replace
Replace text in watch key slash
■ watch_key_at replace
Replace text in watch key dot
■ watch_key_space replace
Replace text in watch key at
■ watch_key_left_angle replace
Replace text in watch key space
■ watch_key_right_angle replace
Replace text in watch key left angle
■ watch_key_plus replace
Replace text in watch key right angle
■ watch_key_equals replace
Replace text in watch key plus
■ watch_key_question replace
Replace text in watch 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_jira_issue_comment_closure_watch core.storage.shared.write
Write storage shared
skip: step.skip_closure_seed equal true
■ summary to_summary
Format results as a summary card
▼
Output
summary summary
Settings 4 configurable

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

cloud id setting =
comment text setting =
issue id or key setting =
no response timeout days setting = 30

Uses (4 operations)

Pack operation Read issue on jira recued-core.jira.issue.read
Pack operation Search comment on jira recued-core.jira.comment.search
Pack operation Add comment on jira recued-core.jira.comment.add
Shared store Write storage shared core.storage.shared.write

Trust & control

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

Permissions it requires

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

What it's allowed to do

Write Shared store core.storage.shared.write external change

3 more aren't listed here. You'll see them at install.

Data it touches

SurfacesShared store
Warehousedata.shared

About

Tags

jira jiraatlassianissuescommentswork-trackingproject-managementapprovalclosed-loopstate:jira-issue-comment-closure-watcherpack:jira-issue-comment-closure

Details

37 steps 4 configurable settings recipe_id: comment-issue-with-closure-jira