Jira my issues digest
Scheduled read-only digest for personal Jira work. It reads the current Jira user, assigned issues, optionally reported issues, and optionally recently updated issues through recued-core.jira, renders a compact table, and can send an in-app nudge when matching issues exist. It does not create, edit, transition, assign, delete, attach, notify, or call arbitrary Jira endpoints.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (21 steps)
me
?
assigned_raw
?
reported_raw
?
skip: config.include_reported not_equal true
recent_raw
?
skip: config.include_recently_updated not_equal true
assigned
default
Apply default
reported
default
Apply default
recent
default
Apply default
issues
flatten
Flatten nested lists in
assigned_count
count
Count items in assigned
reported_count
count
Count items in reported
recent_count
count
Count items in recent
issue_count
count
Count items in issues
has_issues
compare
Check if issue count is greater than 0
notify_enabled
compare
Check if setting notify when matches equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
rows
slice
Take a subset of
issue_keys
pluck
Extract key from each item
issue_keys_text
join
Join items with ", "
table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
channels
setting
=
in_app
cloud id
setting
=
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
atlassian
setting
=
row limit
setting
=
25
start hour
setting
=
8
include reported
setting
=
true
notify when matches
setting
=
true
include recently updated
setting
=
true
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.