Ext Ops Panel
Open dashboard
Permissions and history

Is Bug Reporter for Jira safe to install?

Bug Reporter for Jira asks for 5 browser permissions and 5 site patterns. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Bug Reporter for Jira

Chrome extension · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
Declares it collects none
Audience
39 users

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares 5 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

39 users

Users
+4 since 01.09
34-43 · 29 readings
  1. 2026-09-0135
  2. 2026-09-0238
  3. 2026-09-0638
  4. 2026-09-0739
  5. 2026-09-0938
  6. 2026-09-1342
  7. 2026-09-1540
  8. 2026-09-1741
  9. 2026-09-2043
  10. 2026-09-2240
  11. 2026-09-2641
  12. 2026-10-0536
  13. 2026-10-0834
  14. 2026-10-0937
  15. 2026-10-1037
  16. 2026-10-1339
  17. 2026-10-1640
  18. 2026-10-1842
  19. 2026-10-1941
  20. 2026-10-2039
  21. 2026-10-2142
  22. 2026-10-2240
  23. 2026-10-2341
  24. 2026-10-2440
  25. 2026-10-2538
  26. 2026-10-2840
  27. 2026-10-2938
  28. 2026-11-0139
  29. 2026-11-0339

What the store shows

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

The store lists no publisher name, who publishes 3 listings we track. This listing has been in the store since 2025-06-05 and was last updated on 2025-06-05.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. JIRA Bug Report Formatter Runs its code on every site · 3 permissions, 3 site patterns 7 users
  2. JBug — Bug Reporter for Jira Access to specific sites only · 4 permissions, 4 site patterns 14 users ★ 5.0
  3. Bug Reporter Runs its code on every site · 5 permissions, 6 site patterns 21 users ★ 5.0

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Bug Reporter for Jira access?
Every site you visit. This extension can read and change the content of any page you open. It declares 5 browser permissions.
What data does Bug Reporter for Jira collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Bug Reporter for Jira asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Bug Reporter for Jira publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-03.

Back to Bug Reporter for Jira · Alternatives to Bug Reporter for Jira

Where the data comes from: how the catalog is built