Skip to main content

ACC Issues

ACC issues, with the model attached.

Aging, ownership, and root cause, next to the element the issue is about.

ACC answers “what is open right now” well. It is less good at “is this getting better”, which needs history, aging, and a way to slice by something other than status.

How it’s made

Issues reach Frame on a webhook, so the report follows the project rather than a manual sync. They land as a properly typed table — dates are dates, counts are numbers — which is what makes aging analysis possible without a layer of conversion steps.

How Frame builds it

Raised in ACC, already in the report

Issue in ACC raised or updated Webhook no manual sync Typed table dates stay dates Aging, owner, root cause every lifecycle date, as a date Markers in the viewer pinned where it was raised
Issues arrive on a webhook rather than a manual sync, and they keep the coordinates they were pinned at — so the chart and the model stay in step.

Every lifecycle timestamp comes through, alongside type, subtype, root cause, and your project’s custom attributes: days open by assignee, time to close by type, recurring causes seen as patterns. Issues also keep their coordinates and element references, so the Issues page can put one on the geometry it concerns. A federated variant handles issue sets spanning several models in a coordination view.

Datasets in this report

FRAME_Issues
One row per ACC issue with typed columns — status, priority, assignee, type and subtype, root cause, all lifecycle dates, comment and attachment counts, official response, and custom attributes.
FRAME_Assets
Frame's element table, joined to issues by object and external ID so an issue resolves to a specific element.

Read more

Build reports that drive action

Discover the benefits of Frame today.