Exciting news for all our Flare users! Previously, you could sync GitHub issues with Flare errors. Many loved this integration; it allows teams to quickly respond to bugs reported in Flare and keep track of the issue progress in GitHub. When the issue is closed in GitHub, Flare automatically closes the associated error.
We've had countless users asking for a similar feature but with Jira, the all-in-one bug tracking and project management solution from Atlassian. Just like GitHub, it allows you to create issues for bugs and track the progress your team has made in resolving them.
We're proud to present the Jira integration within Flare today! Let's go through some of the features.
Integrating Jira projects with Flare projects
You get started by connecting a Jira team with your Flare team. After that, within the Flare project settings, you can connect a Jira project with a Flare project:

You also need to select an issue type that will be used to report errors.
When you've connected the Jira and Flare projects, you will be able to configure how the integration will work:

-
Should Flare URLs in Jira issues automatically link the Flare error with the Jira issue?
-
When an issue status is changed to or from a certain status, should the Flare error be resolved or unresolved?
-
Should the Jira issue change to a certain status when a Flare error is resolved or unresolved?
All these options are configurable! It is even possible to connect multiple Jira projects with one Flare project.
Jira in Flare
When you've configured your Flare project to work with Jira, you'll get a new button on each error:

Here, you can see all the Jira issues connected with this error and immediately create a new issue:

Already have an issue within Jira? No problem! Just use the URL of the issue to link it with the error:

When an issue is linked to an error, we automatically track it. When the status changes, you'll see this reflected in Flare. That's neat!
Flare in Jira
Lastly, when in Jira, you'll see a new panel on your issue detail view called "Flare." Here, you can see all the Flare errors this issue is linked with:

Conclusion
We're thrilled to release this Jira integration finally! You'll find more information about it here. Check it out and let us know what you think about it.
As a small teaser for next week, we will reveal another integration. Stay tuned!
Continue reading
Why we removed AI solutions from Flare
AI generated solutions are dead, long live AI generated solutions! We removed the old one-shot fixes from a model that could only see the stack trace. It simply couldn't compete with modern agentic AI. In their place, Flare works with the agentic AI tools you already use: an MCP server that handles real triage, a CLI with an agent skill, quick Copy for AI prompts in the UI and docs served as markdown. Hosted agents are in the works too.
Alex
Flare now uses OAuth for MCP, the CLI, and API
Connect MCP clients like Claude and Cursor to Flare by logging in from your browser, no more copying API tokens. Every connection gets its own permissions, so you can give your AI read-only access to a single project. The CLI signs in the same way, and new personal access tokens with scopes and expiry cover scripts and CI.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates