MetaLens360Help Center

Track promotions and the change narrative

See where each change has reached in your promotion pipeline, what is blocked or stranded, and ask plain-English questions about what changed and where it is live.

Updated in Source control & promotion

Overview

Two tabs on Source Code Repo Insights answer release questions:

  • Promotion — where each change has reached in your pipeline, and what is stuck.
  • Change Narrative — what changed in a time window, grouped into functional changes, with each one checked against what your orgs are running now.

MetaLens360 has no CI/CD integration. It reports where a change has arrived in the repository and what each org currently holds — not deployment events.

Before you start

  • Promotion needs a promotion pipeline for the repository. See Set up a promotion pipeline.
  • Running a promotion sync needs the Run sync on demand permission (every role except Viewer by default).
  • Change Narrative uses your AI providers to group commits. Without AI it still lists commits, just uncorrelated. See Configure AI providers.

Steps

Track promotions

  1. Open Source Control → Source Code Repo Insights and click Promotion.
  2. Choose the Repository. The pipeline decides which branches matter, so the branch picker doesn't apply here.
  3. The first time, click Sync promotion history. It backfills 180 days of branches, pull requests and tags, and keeps running if you leave the page. Later, click Sync to fetch only what's new.
  4. Pick a window (30d, 90d, 180d, 365d) and read the Executive view: In pipeline, Completed, In flight, Blocked, Median end-to-end and Undetermined. A Bottleneck line names the slowest stage.
  5. Check Out of sync (in one stage but missing from the next) and Longest running (incomplete changes, oldest first).
  6. Switch to Change journeys and filter by ticket key, commit hash or subject to follow one change. Each stage shows Promoted, Pending, Blocked, Not yet reached or Unable to determine.
  7. Type a question in the ask box, such as "Did ACME-142 reach Production?", and click Ask.

Read the change narrative

  1. Click Change Narrative and choose a Repository and branch.
  2. Pick a window chip such as last 30 days, type a phrase like "between Aug 1 and Aug 15", or click Custom dates….
  3. Click Analyse changes. Analysis only runs when you click it; reopening the page shows your last result.
  4. Read each change card. The Currently in chips show how many of its components each org holds. Click Details, then Show per-org detail for live, differs, not present or not indexed per component.
  5. Ask follow-up questions in the box, such as "Who worked on pricing?", and click Ask.

How sure is MetaLens360?

EvidenceLabel
Same commit, or same subject and authorconfirmed
A merged pull request with the same ticketlikely
Only a ticket referencepossible — check it

Example

On release day, Priya asks "Did ACME-142 reach Production?". The answer says it is Promoted to UAT with confirmed evidence but Pending on main. Out of sync shows two more changes waiting at the same stage, so she merges the open pull request.

FAQs

What does "Undetermined" mean?

At least one stage can't be seen — almost always a branch that hasn't been synced, not a promotion problem.

What does "not indexed" mean in Change Narrative?

MetaLens360 can't see that org's copy of the component. Sync the org to make it comparable. It does not mean the component is missing.

Troubleshooting

"No promotion pipeline is configured for this repository"

Click Configure it in Settings → Promotion Pipeline and create one.

"… is configured, but no history has been read yet"

Click Sync promotion history.

A "not correlated" chip appears

No AI provider answered, so commits are listed as committed. The data is still accurate. See Configure AI providers.

"Sync failed. Check the repository connection and its token."

See Fix Git repository access.

Was this article helpful?

Related articles