When an error pops up in Flare, you can turn it into an issue on GitHub, GitLab or Linear with a single click. Handy, but until now that issue landed in your tracker a little naked. No assignee. No labels. Nobody knew who should pick it up.
So you'd create the issue in Flare, switch to GitHub or Linear, assign the right person, slap a bug label on it. Every single time.
That's a few clicks too many. Let's fix that.
Pick assignees and labels while you create
From today, when you create an issue from an error you can choose the assignee and labels right there in Flare. On Linear you can also pick the project the issue should land in.

The dropdowns are filled with the people, labels and projects from your connected issue tracker. So whatever you'd normally pick over there, you can now pick here.
Set defaults per project
In most projects the bug label will be the same, just like the assignee for the error. So you can set defaults that get used the next time an issue is created.
Of course you're totally free to overwrite these defaults when creating an issue.

This works on GitHub, GitLab and Linear today. Due to some bigger Jira refactors we're working on, defaults didn't make it into this round, yet you can already provide values for custom fields. Defaults for Jira will be added later this year.
Let us know what you think. Happy debugging!
Continue reading
Bringing Flare back to Laravel 10 and PHP 8.1
Flare now supports Laravel 10 and PHP 8.1 again, so older apps get performance monitoring and logs too. Here’s how we did it.
Ruben
Your Laravel routes can carry metadata now, and Flare shows it
Laravel added a new way to attach metadata to routes, and Flare now automatically shows it on errors and traces
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates