-
Suggestion
-
Resolution: Unresolved
-
None
-
43
-
39
-
Problem Definition
Currently, the Jira analytics collection can be disabled from "Administration - > System - > Advanced - > Analytics" and this will stop processing and uploading analytics logs to Atlassian by Jira.
That being said, this does not stop POST rest call "/rest/analytics/1.0/publish/bulk". This unnecessarily floods the access logs and creates confusion about the feature status.
Suggested Solution
Stop firing "/rest/analytics/1.0/publish/bulk" from Jira frontend.
Workaround
None
- duplicates
-
JRASERVER-77646 Even when we disable Jira Analytics, we are sending requests to /jira/rest/analytics/1.0/publish/bulk
-
- In Progress
-
- is related to
-
JRASERVER-41593 JIRA throws /rest/analytics/1.0/publish/bulk for Inline Edit events when Analytics is Disabled
-
- Closed
-
-
JRASERVER-77793 Improve Dependency Handling for "Analytics Client" plugin
- Gathering Interest
- relates to
-
JRASERVER-77646 Even when we disable Jira Analytics, we are sending requests to /jira/rest/analytics/1.0/publish/bulk
-
- In Progress
-
-
JRASERVER-77560 Analytics threads are running even though analytics is disabled
-
- Gathering Impact
-
-
JRASERVER-70361 Jira have outgoing connections even though disabled Analytics
-
- Waiting for Release
-
[JRASERVER-70086] Disabling Jira Analytics should stop sending POST requests to /jira/rest/analytics/1.0/publish/bulk
UIS | Original: 52 | New: 43 |
Fix Version/s | Original: 9.12.23 [ 112308 ] | |
Fix Version/s | Original: 10.3.6 [ 111093 ] |
Fix Version/s | New: 9.12.23 [ 112308 ] |
Fix Version/s | New: 10.3.6 [ 111093 ] |
Support reference count | New: 39 |
Link | New: This issue duplicates JRASERVER-77646 [ JRASERVER-77646 ] |
PM Reviewed | New: 15/Apr/2025 | |
Status | Original: Gathering Interest [ 11772 ] | New: In Progress [ 3 ] |
UIS | Original: 43 | New: 52 |
Assignee | New: Oleksandr Karabush [ c7dff132d920 ] |
Hi everyone,
Thank you for taking the time to file and comment on this issue. We've reviewed it and agreed it’s a high priority for us to resolve. Our engineers have already started working on the issue.
Please continue watching this ticket for future updates and changes in the timeline that may impact your work.