Community
Q&A
Jira
Questions
Jira automation : Get items from other projects to compile a daily report

Jira automation : Get items from other projects to compile a daily report

Hello everyone,

Since last week, I try to automate a short report about my daily actions.
In the final report sent via Google Chat, I would like to have a list of items (e.g. Test Execution) from Project A and another list of items (e.g. Bug Build) from Project B.

I have already managed to retrieve the data from Project A and send it to Google via the webhook, as my automation is configured in Project A. And it works well.

Capture d’écran 2026-07-16 113812.png

I spoke to the Jira admins about adding Project B to the automation using the ‘Multiple projects’ feature. However, I am now unable to edit the automation; all the fields are greyed out, even though I am an administrator on both projects.

From what I’ve understand in this ticket (https://jira.atlassian.com/browse/JRACLOUD-92590), it seems that, for the moment, it’s not possible for someone who isn’t a ‘Jira admin’ to manage this automated process.

Do you have any solutions to ‘get round’ this issue?
For example, is it possible to link automated processes across different projects and consolidate the data to send a bulk email?

5 answers

1 accepted

0 votes

Answer accepted

Hi @20103585 -

Marc @Marc -Devoteam- is right that the multi-space rule needs a site-level Jira admin - project
admin on both is not enough, that is JRACLOUD-92590 exactly. Worth adding why the
obvious workaround does not save you: if you keep the rule single-project and try to
Lookup issues with project = B, Jira silently appends the rule's own scope to your
JQL, so it becomes project = B AND project = A and returns nothing. Cross-project
lookup genuinely requires the rule scope itself to be global or multi-project.

So you have two honest paths:

- One consolidated message, one rule: this has to be a global/multi-project rule,
which means a site admin. No way around the admin on this one - but it is a
five-minute change for them (System > Global automation), so the ask is small. Note
global rules count against your plan's monthly automation limit, unlike project
rules which are unlimited.

- Stay project-admin only: keep two separate single-project rules, one in A and one
in B, each posting to the same Google Chat webhook. You lose the single combined
message - you get two posts in the same space instead - but you never touch
site-admin and you own both rules outright.

If the daily report just needs both lists to land in the same channel, the two-rule
route is usually the pragmatic one. If it must be one message, it is worth the short
site-admin request.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

HI @20103585

If the scope of the automation rule spans multiple spaces (projects), only Jira admins can make changes to such a rule.

And yes, you can lookup issues from multiple spaces and then send this information in a single email.

See this KB article and the example that is used, https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Hello @20103585

The other option is to not send the output to Google Chat at all.

Create and save a filter that selects all the items you want from the various projects.

Create a Subscription to that filter to periodically run it and send you the results via email.

Find another method to get the email content from the email message to Google Chat.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Thanks everyone for your answers. For now, I will probably create separated automation but keep in mind Zhade.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hi @20103585 ,

There is also an alternative approach that does not require configuring a cross-project Jira Automation rule.

With Zhade, you can bring data from multiple Jira projects into Google Chat in two ways:

Schedule a JQL-based daily report
You can create a report using a JQL query that includes the required items from Projects A and B, and schedule it to be sent to a Google Chat space.

Setup guide:
https://zhadelabs.atlassian.net/wiki/spaces/ZCD/pages/83034115/Schedule+Daily+Report

Receive issue updates in a daily notification thread
You can configure a Google Chat space with the required JQL query and enable the Daily Notification Thread option. Updates for all matching issues will then be collected in one daily thread instead of being posted as separate messages throughout the day.

More details:
https://zhadelabs.atlassian.net/wiki/spaces/ZCD/pages/32047180/Daily+Notification+Thread

This requires installing the Zhade app on the Jira instance, but it may also be useful for the wider team if they want to receive Jira notifications and interact with Jira issues directly from Google Chat.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

For clarity, here is the link to the app listing in the Atlassian Marketplace, where you can find pricing and support information for the app.

Zhade Integration for Jira & Google Chat

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

Suggest an answer

Was this helpful?

Thanks!

Jira

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

ENTERPRISE

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Jira automation : Get items from other projects to compile a daily report

5 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Community showcase

Atlassian Community Events