Trouble with Jira Issues macro

Andrew Antares
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 24, 2024

I have been using the Jira Issues macro successfully for months to create dashboards for my team. Recently a strange problem popped up.

The query I use contrains the issues to belong to specific assignees:

"project in (Project 1) and assignee in (Team Member X, Y, Z, etc) and sprint in openSprints() AND status != Done AND status != Backlog and status != Abandoned and issuetype != Epic and issuetype != Story

Recently, two issues from Team Member Alpha have been showing up on ALL other instances of the macro that pull issues from Project 1. The issues are definitely not assigned to Alpha, the JQL definitely identifies X, Y, Z, etc as the assignees, and I have not made any recent changes to the JQL.

The extra weird part is that the two issues associated with Alpha are subtasks from two different stories. X, Y, Z, etc all have subtasks under these stories, but the subtasks from those stories that SHOULD be picked up by the macro for X, Y, Z etc isn't being picked up anywhere.

So, across every board (even new boards, I tried starting fresh) are picking up these same two subtasks assigned to Alpha.

The workaround is that I use "AND assignee != (Alpha)" and that clears out the issues from the wrong person. To pull in the missing issues that should be found by the query, I use "labels = (custom label I made for each person and each missing subtask)." This workaround solves the current problem but is not sustainable.

Any troubleshooting tips out there?

1 answer

1 vote
Shawn Doyle - ReleaseTEAM
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 24, 2024

This looks more like a Jira question than a Confluence one.  I was about to move this to the Jira forum for better visibility, but you did start out with the "Jira Issue Macro".

However, for us to be able to troubleshoot, please post your exact JQL and we can see where you might be having an issue.  

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events