Pushing Findings to Forma Issues
Learn how to push QA violations from Foreman to Forma Issues, choose grouping modes, set defaults, and manage issue creation with auto-sync and AI-assisted details.
Why push to Forma Issues?
Foreman is for finding the problem; Forma Issues is where your team tracks the fix. Pushing turns each QA violation (or a group of related violations) into a real ACC issue with an assignee, due date, source-file link, and a live two-way status link back to the original check result.
How to push
- Open a completed check run from Check History.
- Tick the checkbox next to one or more file rows. The selection action bar appears at the bottom.
- Click Push to ACC. The dialog opens with sensible defaults:
- Issue type / subtype auto-selects "Quality" if your project has it; otherwise empty until you pick.
- Due date is empty by default (the value you last picked is remembered as a relative offset — e.g. 7 days from today).
- Auto-sync and Attach the source file are on by default.
All defaults persist per project after a successful push, so the next time you push for the same project you start from your last configuration.
Grouping options
Decide what shape the issues should take:
| Mode | Best when |
|---|---|
| Per violation | Each finding needs its own assignee, due date, and closure tracking. |
| Per file | A single file owner needs to fix everything on that file in one pass. The file is attached once. |
| Per rule | One coordinator should fix the same problem (e.g. "missing revision number") across many files. All violating files are attached to one issue. |
| Per modifier | Group everything modified by the same person — that person becomes the default assignee for the bundled issue. |
The Issues to be created list updates live as you switch modes.
Per-row controls
In the preview list each issue shows the title, file/rule/severity context, and the assignee chip:
- Use AI — if you click the wand icon next to a row, Foreman drafts a title and description for that issue and auto-ticks the Use AI checkbox. Untick it any time to fall back to the templated text.
- Edit — expand the row to override title/description by hand and to pick a different assignee from the project members dropdown (filterable by name or email). Each issue's assignee defaults to the file's last modifier when matched.
Source files
When Attach the source file(s) is on:
- Forma files — the issue description gets a "Source files in Forma" block with one direct link per unique violating file. Reviewers click through to view the file in Forma.
- Local-uploaded files (only for runs that included local PDF uploads) — the actual PDF is uploaded as an issue attachment using the standard ACC attachment flow (storage → signed S3 → finalize → link).
Failures are non-fatal — the issue is still created even if the attachment step fails.
Auto-sync webhook
When Auto-sync ACC issue status is on (default), the first push to a project quietly registers a Forma Issues webhook for that project. After that, any status change in Forma flows back into Foreman:
| Forma status | Foreman violation becomes |
|---|---|
closed, answered, completed |
Resolved |
open, draft, in_review |
Open |
deleted |
Open (issue link is gone, violation stays visible) |
in_dispute, not_approved |
Open |
When an issue is reopened, the run-detail page shows a snackbar the next time it loads:
Forma issue #801 was reopened — its linked violation is back to Open.
You can manage all webhook subscriptions on the Webhooks page, where you can pause, delete, or inspect the recent events for any trigger.
Already-pushed protection
Foreman tracks every push, so you can't accidentally create duplicate issues. Re-selecting a row whose violations have already been pushed shows a snackbar instead of opening the dialog. To force a new push, first delete the existing tracking row from the Webhooks page (or push a different selection).
Manual sync
If a webhook event was missed (subscription was paused, network blip, etc.), click Sync Forma at the top of the table. Foreman calls Forma once per linked issue, refreshes status + display ID, and re-applies the violation status mapping above.
Reports
CSV, Excel, and PDF exports automatically include Forma Issues, Forma Issue Status, and Forma Issue Links columns when any rows in the export have been pushed. The PDF report also lists linked issues under each file in the Detailed Results section.
Next steps
- Understanding Check Results — the run detail page surfaces and badges
- Exporting Results & PDF Reports — full export reference
- Managing Webhook Triggers — view, pause, or delete webhooks