Reference · built on requestOperator by FibricReporting & analysis

Weekly Review

The weekly operations review assembled from period numbers, open exceptions, and last week's commitments, proposed as a document.

Request accessPricing ↗

About

The weekly review is the same document every week with different numbers and a list of promises nobody has re-read. This operator assembles it. It reads the period's figures from the warehouse tables you register. It reads open exceptions from your work tracker: issues matching a saved JQL query in Jira, or tasks in a named Asana project. It reads last week's review page and the commitment tasks it created, and checks which are done.

It proposes the new review as a draft page in Confluence or Notion, with a commitments table showing kept, missed, and carried over. Approved commitments become tasks. The link is posted to the meeting channel once.

This is a reference listing. It documents what Fibric would read from Weekly Review and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Period figures from tables or views registered in Snowflake, BigQuery, or PostgreSQL, for the week just closed and the one before
  • Open exceptions returned by a saved JQL query through the Jira search endpoint, with status and assignee
  • Tasks and their completed state in a named Asana project, including who they were assigned to and when
  • Last week's review page in Confluence or Notion, and the commitment tasks it created
  • Changelogs on commitment issues in Jira, to see when each moved and by whom
  • The meeting channel, so an already-posted link is not posted again

Proposed actions

  • Target capability: propose the review as a draft page in Confluence or Notion, with each figure linked to its source table
  • Target capability: propose one task per new commitment in Jira or Asana, assigned to the person named in the review
  • Target capability: propose carry-over of a missed commitment with its original date and the reason recorded
  • Target capability: propose a message to the meeting channel with the page link, sent once after the page is approved

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Confluence page from Snowflake and Jira

    Period figures from Snowflake and open issues from a saved JQL query are assembled into a draft Confluence page. New commitments become Jira issues on approval, each linked back to the page.

    With Snowflake, Jira, Confluence

  • Notion review with Asana commitments

    The review is proposed as a Notion page under your operations parent. Commitments are Asana tasks with due dates; last week's tasks are read back to mark kept or missed.

    With Notion, Asana, BigQuery

  • Post the link once

    After the page is approved, one Slack message with the link is proposed to the meeting channel. The message id is kept so the same page is never posted twice.

    With Slack, Confluence

  • Carry the misses forward

    A commitment not done by review day is proposed for carry-over with its first due date shown. Repeated carry-overs are flagged in the page for discussion.

    With Jira, PostgreSQL

Requirements

  • A warehouse connector holding the period figures: Snowflake, BigQuery, or PostgreSQL
  • A work tracker with a query or project that defines open exceptions: Jira, Asana, or Linear
  • A document space for the review page: Confluence, Notion, or Google Drive
  • A saved query or project for exceptions, a template for the page, and the channel for the link
  • A named owner for each section, so unowned commitments cannot be created
Authentication
Write scopes on the document space and work tracker (write:page:confluence, write:jira-work, or the Notion insert-content capability), read on the warehouse, and chat:write for the channel.

Limits

  • Confluence creates pages as published unless status is draft. It proposes drafts; a person publishes.
  • Notion accepts up to 100 child blocks in one create call. A longer review is written in more than one call, each recorded.
  • Jira search results can lag recent edits. A commitment closed minutes before the run may show as open.
  • It reads the review template you give it. It does not write narrative beyond the sections that template defines.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Weekly Review ↗

Questions and answers

What do I approve, and in what order?
The draft page, then the commitment tasks, then the channel message. Each is separate. You can approve the page and reject a task. Nothing is created in the tracker or posted until each step is approved.
What does the record hold?
The page id and version, every figure with its source table and query, each task created with its assignee, the carry-overs and their reasons, and who approved each step and when.
What will it never do on its own?
It never publishes a page, closes or reassigns an existing task, edits a prior review, or posts to the channel. If a source is missing at run time the page says so in that section.
Ask about Weekly Review

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy