nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Help with {{lookupIssues}}

Alicia_a9jjyu

Absolutely stumped trying to create a filtered list in 1 Card for a Kanban

Every Monday

Create 1 card of all the late cards for the week

Link all the late card to this 1 card

The logic in place create a card for each late card. I can use this logic if I’m emailing multiple late notifications, but the manager just wants 1 card a week.
I have tried in a branch & without a branch

Most recently created issue, current issue

So far the schedule & filter works.

When: Scheduled Every Mon

filter: Project = ABC AND Status not in (Done, Cancelled) AND duedate <-1

then Create a new

Story

Edit Description

{{#lookupIssues}}
* {{key}} {{issue.summary}}
{{/}}

Accepted answers

Bill Sheboy

Hi @Alicia -- Welcome to the Atlassian Community!

Are you trying to create a weekly report of items which were due in the past?

Perhaps try a saved filter, and allow people to subscribe to it to get a single email with the items rather than using an automation rule to create an issue to track the items.

If you still want to use an automation rule to send that email report, that is possible. What version of Jira do you have: Cloud, Server, or Data Center? That will impact the approach used to send the email report.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Alicia -- Welcome to the Atlassian Community!

Are you trying to create a weekly report of items which were due in the past?

Perhaps try a saved filter, and allow people to subscribe to it to get a single email with the items rather than using an automation rule to create an issue to track the items.

Kind regards,
Bill

Alicia_a9jjyu

I think it’s cloud. I proposed subscribe but the manager is set on having it in a card. He wants all the past due cards linked to his weekly card.

Bill Sheboy

Please consider meeting with that manager and your team agile coach (or Jira admin) to understand why they want an issue on the board to manage this. That may reveal another approach, such as a dashboard or quick filter for the board.

The reason I suggest this is:

This situation indicates a training opportunity for the manager to learn more about Jira usage, Kanban practices, and team autonomy vs. accountability
The team uses a board to manage their work and make progress visible. Adding an item to the board for the sake of reporting will cause confusion.
As your rule is scheduled to run daily, this will continue to add new items...some containing the same Jira issues as the prior days
Adding reporting items to the board will inflate / alter the built-in Jira reporting, making it harder for the team to use those reports to improve how they work
Finally as the team is using Kanban, this approach is in opposition to a fundamental idea of Kanban methods: pulling new work versus pushing it on the team.

Assuming you have the conversation above and still want to do this, try adjusting your rule as follows:

trigger: scheduled with no JQL
action: lookup issues with the JQL you were using
advanced compare condition:
- first value: {{lookupIssues.size|0}}
- condition: greater than
- second value: 0
action: create your issue

Alicia_a9jjyu

Thank you so much

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

unknown-hosting-type