Use “Create Jira issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Create Jira issue with closure watch
Use “Create Jira issue with closure watch” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Jira Issue Closure Loop
4 pinned recipes
Use Jira Issue Closure Loop in Recued for atlassian, issues, work tracking, and project management. 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 “Jira issue closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.
Use “Jira issue 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 “Jira issue 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 (31 steps)
cloud_id_value
trim
Trim whitespace from setting cloud id
project_key_value
trim
Trim whitespace from setting project key
issue_type_value
trim
Trim whitespace from setting issue type
summary_value
trim
Trim whitespace from setting summary
description_value
trim
Trim whitespace from setting description
has_connection
compare
Check if connections atlassian has data
has_cloud_id
compare
Check if cloud id value has data
has_project_key
compare
Check if project key value has data
has_issue_type
compare
Check if issue type value has data
has_summary
compare
Check if summary value has data
skip_issue_create
any
Check if any of the conditions are true
created_issue
recued-core.jira.issue.create
Create issue on jira
skip: step.skip_issue_create equal true
defaults
defaults
Apply defaults
created_issue_ref
default
Apply default
has_created_issue_ref
compare
Check if created issue ref 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_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
Configurable at install. Defaults shown — change them anytime in Recued.
summary
setting
=
cloud id
setting
=
issue type
setting
=
Task
description
setting
=
project key
setting
=
no response timeout days
setting
=
30
Uses (2 operations)
Pack operation
Create issue on jira
recued-core.jira.issue.create
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
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
1 more isn't listed here. You'll see it at install.