Using Rovo to Roll Up and Post Project Status Updates

[Gabriel Rojas]

Hi Atlassian community,

I’m trying to streamline project reporting by using Jira’s Cloud issue hierarchy like this:

Initiative (used like a Project)
└── Epic
    └── Task / User Stories

Each issue is connected via the Parent relationship. We are actively using fields like Baseline Start Date, Baseline Due Date, and Due Date.

What I’d like to do is have Rovo or Jira AI automatically generate a “Project Status” comment, based on the current Status of all child issues (Epics, Tasks, etc.) — and then post that comment in the Projects Directory (under the Initiative/Project view) regularly (e.g., weekly).

This wouldn’t need to be real-time. I’m happy with a scheduled automation that:

1. Pulls all child statuses for each Initiative.

2. Generates a readable project summary.

3. Posts that as a comment in the Initiative’s entry on the Projects Directory.

Has anyone tried something similar using Rovo, Jira Automation, or any AI-assisted approach?

Would love any advice or pointers on how to structure this — especially if this is something Rovo can handle out of the box.

Thanks in advance!

[Tomislav Tobijas]

Hi @Gabriel Rojas ,

This is actually something we would need to explore as well as we have something similar in the Jira hierarchy 'connected' with the home projects.

In one implementation, we have filters such as:

issue IN portfolioChildIssuesOf("ABC-44") OR KEY = ABC-44

where we also have 2 hierarchy levels above Epics, and with this filter you can pull everything below ABC-44 (incl. same item).

With this approach, I guess you could use Rovo and point it to this specific filter so it looks at the item statuses and creates a summary for that project.
Without a filter, you could maybe point to the Rovo agent that, if you give it just an initiative key, it would look at child items by using the same approach.

Hope this could give some insights (and I'm keen to hear more about possible solutions).
I'll also move this to Rovo app forum group for other experts to chime in on the discussion.

Cheers,
Tobi