Support
One address, read by a human: hello@lintelworks.dev
We aim to reply within two business days. We're a small operation, so there's no ticket portal and no phone queue — just email, answered by the person who wrote the code.
Before you write
Two questions cover most of what we're asked.
A section says "not checked" — is that a bug?
Usually not. It means the app could not read that part of your site, most often because the feature isn't available on your Jira plan — issue security schemes, for example, are a paid-tier feature. We deliberately show not checked rather than clear in that case, because reporting "nothing found" for something we never looked at would be the most dangerous thing this app could do. If a section stays "not checked" and you think it shouldn't, tell us which one and we'll dig in.
The report is empty for a group I know is in use
Check whether the reference is somewhere we don't yet look. Group Blast Radius currently covers permission schemes, projects (via schemes and roles), notification schemes, issue security levels, and shared filters and dashboards. It does not yet scan workflow conditions, validators, post-functions, or automation rules. If your group is referenced there, we won't find it — that's a known limit, not a failure, and it's on the roadmap.
Reporting a problem
Useful things to include, if you have them:
- What you selected and what you expected to see instead
- Which section was wrong
- Roughly how large the site is — number of projects tends to matter
Please don't send anything sensitive. We don't need it, and we'd rather not hold it.
If you found a false result
Tell us immediately and we'll treat it as the highest priority. The entire value of this app is that its answer can be trusted before you make an irreversible change. A report that misses a real reference is a serious defect, not a feature request.
Security
To report a security issue, write to hello@lintelworks.dev with "security" in the subject. The app is read-only, stores no data, and makes no external network calls — see Privacy for the specifics.