How do you run weekly Jira review from epics, worklogs, and planned dates?

[Max Mykhailenko]

Hi Community,

I’m looking for how PMs and delivery leads actually run weekly Jira review, not a generic reporting template.

Context/disclosure: I’m building Focus Flow, a Jira Marketplace app for epic execution review, so I’m trying to understand where the real workflow breaks. No install link here; I’m looking for patterns and blind spots.

For teams that use Jira epics and log time/worklogs:

- Which screen do you open first for weekly delivery or status review?
- Do you review by epic, sprint, project, or another structure?
- Do worklogs influence the discussion, or are they mainly used for timesheets?
- Where do you compare planned dates vs actual execution?
- What is hardest to answer: what moved, what is risky, or what needs replanning?

I’m especially interested in post-launch ongoing delivery, where feature work, support, feedback, and unplanned work compete for capacity.

If you have a flow that works, I’d like to learn from it. If you have a flow that is painful, I’d like to understand where Jira makes you reconstruct the story by hand.

[Bartek Szajkowski _ Orbiscend OU]

Hello @Max Mykhailenko 

Thanks for your request.

My answer cover only part of your request/issue and it's connect with instal third-party app -> but as you wrote above, I will not put link to this app ;)

JQL Argon app can help you to solve 3 points:

1. "What moved this week?" Argon's changedBy function finds issues that transitioned status in a specific period — no manual scanning:

issue in changedBy("project = DEV", "Status", "2026/05/19", "2026/05/26")

2. "What is risky / stuck?" timeInStatus catches issues lingering too long in a status — great for weekly standups:

issue in timeInStatus("project = DEV", "In Progress", "5d")

3. "What worklogs hit this epic this week?" worklog function filters by user, date range, and time spent — not just "were hours logged," but who logged what and when:

issue in worklog("epic = PROJ-42", "", "2026/05/19", "2026/05/26", "1h")

Where JQL Argon app doesn't close the gap: planned vs. actual date comparison and cross-epic capacity view — those still require a dedicated layer like what you're building with Focus Flow.

The changedBy + timeInStatus combo is probably the closest thing PMs use today in native Jira for "reconstruct the story by hand." Argon makes that reconstruction a saved filter instead of a manual exercise.

Hope my answer will be useful for you.

Greetings

Bartek (JQL Argon app provider)