Weekly Jira overview in Notion

Once a week this workflow runs one Jira search and turns the result into one page in Notion. The search asks for both halves of the week at once: everything that reached a Done status in the last seven days, and everything still open that moved in the same window. The two halves cannot overlap, so the counts on the page always add up.

A code step then splits the issues and counts them twice over: by status, so you can see where the week's work actually sits, and by assignee, so each person's completed and in-flight totals are on one line. It sorts finished work from open work by Jira's status *category* rather than by status name, so a project that calls its final column Shipped or Closed is read correctly without any configuration. Unassigned issues are grouped under "Unassigned" rather than dropped.

The page it creates carries a headline count, the two status breakdowns, the newest issues in each bucket with their keys, and the per-person table — enough to read the week at a glance without opening Jira.

Before the first run, edit the settings at the top: paste the id of the Notion database the entries should go into (the database has to be shared with your Notion integration), and set 'notionTitleProperty' if its title column is not called Name. Leave 'jiraProjectKey' blank to cover every project your Jira account can see, or set it to a key like PROJ to scope the overview to one team. 'lookbackDays' is the window, 'maxIssues' caps the search (Jira allows up to 100), and 'highlightLimit' is how many issues get listed by name under each heading.

Connections needed: Jira (the search) and Notion (the page). A quiet week still creates a page, saying plainly that nothing moved, so a missing entry always means the run itself did not happen.