Catch regressions and fix at scale Pro
Issue trackers: GitHub, GitLab, Jira and Linear
Send tracked fixes to the tool your developers already use, by hand or automatically, and get a comment there when a fix is applied.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Issue trackers are set up under Lumtera → Settings → Issue trackers. Under Send issues to, choose GitHub, GitLab, Jira Cloud or Linear, and only that tracker's fields are shown. Save, then click Test connection. The test only reads from the tracker and never creates an issue. It answers with a line such as "Connected to GitHub: acme/website", or says what to fix, such as a token without the right permission or a project that cannot be found.
Once a tracker is connected, each tracked fix gets a button such as Create issue in GitHub: in the block editor next to the fix's status, in the classic editor's Accessibility box, on the Content screen and in the table on the Fixes screen. When the issue exists, the button becomes a link such as #12 in GitHub or WEB-4 in Jira, and the fix's History records it. Each fix gets one issue, even if two people click at the same moment.
Switch on Create an issue for every new tracked fix and an issue opens each time someone clicks Track fix. Issues are created in the background a few seconds apart, so tracking many fixes at once does not flood the tracker. Each one holds the finding, its severity, the WCAG criterion with a link to the W3C's explanation, the HTML snippet, how to fix it, links to edit and view the page, and a link back to the fix in WordPress.
Why does it matter?
Theme and template problems are fixed by developers, and developers work from their own backlog. A task that lives only in WordPress is easy for them to miss.
What do you get?
- GitHub, GitLab (gitlab.com or your own public GitLab), Jira Cloud or Linear, one connected at a time.
- Create an issue from a tracked fix, or turn on automatic issues for every new task.
- A comment is added to the issue when a fix from Lumtera is applied and verified, or undone.
- The access token is stored encrypted and never shown again.
How does it work?
-
Connect a tracker
Under Lumtera → Settings → Issue trackers, choose the tracker, add its details and a token, then click Test connection.
-
Send a fix
Create an issue from a task, or let new tasks create them for you.
-
Close the loop
When a re-scan confirms the fix, the task closes itself in Lumtera.
Who is it for?
-
Theme and template problems
Findings that come from a theme or a custom block reach the developers' backlog with the markup and the page link they need to reproduce them.
-
Agencies working with client developers
Send fixes into the client's own Jira or Linear project, while Lumtera still confirms each one with a re-scan of the page.
-
Sprint planning
Automatic issues put every new accessibility task where the team plans its work. GitLab and Jira issues carry an accessibility label, so they are easy to filter.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan. Connecting a tracker needs an administrator. The Create issue button is shown to people with the See reports and check the site permission who can edit the post.
- What each tracker needs
- GitHub: the repository and a fine-grained token with Issues: Read and write. GitLab: the GitLab address, the project and a token with the api scope. Jira Cloud: the site address, account email, project key, issue type and an API token. Linear: the team key and a personal API key.
- Tokens
- Tokens are stored encrypted with your site's secret keys and are never shown again, sent in events or written to the activity log. Leave the field empty to keep the saved token. If the site's keys change, enter the token again.
- Requests
- Requests go straight from your site to the tracker, time out after 15 seconds and never follow redirects. The tracker must be reachable from the internet, so a GitLab on a private network cannot be used. When a tracker asks Lumtera to slow down, it waits as long as the tracker says.
- Comments, not closing
- When a fix from Lumtera is applied to the page and its re-check confirms it, the issue gets a comment such as "Fixed by change #123, verified by re-scan", and another if the change is undone. Lumtera does not close or edit the issue itself.
Questions
Something else on your mind? Contact support
Does it need fix tracking?
Yes. Issues are created from tracked fixes, which are part of every Pro plan.
Can I connect more than one tracker?
No, one at a time. Choose the tracker your developers work in under Send issues to.
What if an automatic issue or comment cannot be created?
The Issue trackers screen says why, for example an expired token. If a tracker asked Lumtera to slow down, it is tried again at the time it named. You can always use Create issue on the fix by hand.
Does it work with other tools, such as Asana or Bitbucket?
Not directly. Webhooks under Settings → Integrations can send fix-tracking events as signed JSON to any tool that accepts a webhook, including services such as Zapier or Make.
More in “Catch regressions and fix at scale”
-
Pro
Email and Slack alerts
Hear about it when a publish adds new errors or feedback goes past its target, never twice for the same one, plus a Monday summary and a score history.
-
Pro
Compare scans
See what is new, what was fixed and what is still there between two scans, by check and by site part, with the likely cause marked.
-
Pro
Fixes queue: bulk fixes you review and approve
Propose the same fix on many pages at once — built-in fixes or text you write (and AI drafts, only if you connect an AI provider) — review every change, then apply and undo them in the background.
Issue trackers: GitHub, GitLab, Jira and Linear
Get it with Lumtera Pro
In every Pro plan. Personal is $75 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew