-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
Component/s: Work Item - View (Internal developer use only)
-
3
-
Severity 3 - Minor
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
When clicking from the comments tab to history or all in the activity section of a JIRA issue you will see a 'Communications Breakdown' error. The development tools in Chrome show a 404.
Environment
(Optional - If Applicable)
- JIRA Cloud 7.0.OD-7
- JIRA Server 6.4.X and JIRA 7.x
Steps to Reproduce
- Access https://ecosystem.atlassian.net/browse/ESS-64 without logging in.
- Click the 'History' tab
OR
- Install a fresh clean server instance
- Create a new project and issue
- Change the permission for the project to allow 'anyone' to browse project/administer project
- Log out
- Go to any of the issue from the new project
- Click on the history/activity tab
Expected Results
Show the history/activity tab contents.
Actual Results
For JIRA 6.4.x
The UI throws a 'Communications Breakdown' error with the text
The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation. Close this dialog and press refresh in your browser
Development tools show a 404 error.
-----------------------------------------------------------------------------------
For JIRA 7.x
This gadget cannot be displayed on your dashboard. This could be due to a licensing problem or an application error. If you need this gadget, contact your administrator for assistance. Otherwise, you can remove it from your dashboard
Notes
Logging in solves the problem. So it's something specific
Workaround
If you can log in you'll need to do that.
- is related to
-
JRASERVER-45580 Activity tabs showing error when accessing issue through anonymous user
-
- Gathering Impact
-