Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

ISSUE: Link from Your Work leads to infinity loading

Ivan Trechekas August 13, 2020

1 Open 
> https://xxx.atlassian.net/jira/your-work

2 Find the ticket with the link that has a format 
> https://xxx.atlassian.net/browse/TICKET-1111?focusedCommentId=<id>&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-<id>


3 click on the ticket

4 take an error
We couldn't connect to the issue. And see the infinity loading process.

It starts adding "&" to the URL 

https://xxx.atlassian.net/browse/TICKET-1111?focusedCommentId=<id>&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-<id>&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&...

and a lot of requests in the Network tab.



I see the error 

  1. Request URL: https://xxx.atlassian.net/rest/internal/2/log/safe/warn
  2. Request Method: POST
  3. Status Code: 204

    {"sentFrom":"jira.frontend.global-loading-bar","message":"Loading bar failed to initialise in SSR. This may be because SSR failed or a bug in the loading bar code.","event":{},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T19:31:44.149Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.issue.data.provider.epic","message":"UPDATE_PREVIEW_REQUEST: dataProvider issue data lookup failed IssueDoesNotExistOrNoPermission","event":{},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T20:08:10.292Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.issue.data-provider.api","message":"tried to populate cache with insufficient field data","event":{},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T20:08:10.294Z","browserName":"Chrome","browserVersion":"84.0"}


  1. Request URL: https://xxx.atlassian.net/rest/internal/2/log/safe/error
  2. Request Method: POST
  3. Status Code: 204

    {"sentFrom":"jira.frontend.spa.view.routes.issue-view.gira.getData","message":"An error was thrown while prefetching issue gira data","event":{"message":"Failed to fetch","stack":"TypeError: Failed to fetch"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T19:32:02.582Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.issue.fetch.issue-fetch-epic","message":"FETCH_ISSUE_REQUEST: Failed to fetch issue data","event":{"message":"Failed to fetch","stack":"Error: Failed to fetch\n at t.selector (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/async-issue-app~issue.45f0857e25f2c6792917.8.js:115:160)\n at t.error (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/vendor~31ecd969.eb94999b89eb23bc89ed.8.js:25:158587)\n at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/vendor~31ecd969.eb94999b89eb23bc89ed.8.js:25:95703","type":"fetch","app":"issue","eventNameSuffix":"issue.error","name":"AnalyticError"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T19:32:02.586Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.portfolio.services.plan-item-visibility","message":"Error while fetching plans visibility","event":{"message":"Failed to fetch","stack":"TypeError: Failed to fetch"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T19:32:30.219Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.navigation-next.page-visit-tracker.project.recent","message":"There was a problem saving recent visited project","event":{"message":"Failed to fetch","stack":"TypeError: Failed to fetch"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T19:32:30.220Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.spa.router.resources.navigation","message":"fetchSidebarConfig","event":{"message":"Fetch call failed with status code: 404","stack":"i: Fetch call failed with status code: 404\n at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/commons.1e50bca47ba4dbac4c81.8.js:12:237610\n at async getData (https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/jira-spa.0ef0264099832242467e.8.js:103:29604)","name":"i","statusCode":404,"traceId":"e72289fefc14d1b8"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T20:07:58.098Z","browserName":"Chrome","browserVersion":"84.0"}

    {"sentFrom":"jira.frontend.resources.issue_media_read_perm","message":"i: Fetch call failed with status code: 404","event":{"message":"Fetch call failed with status code: 404","stack":"i: Fetch call failed with status code: 404\n at https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/commons.1e50bca47ba4dbac4c81.8.js:12:237610\n at async https://jira-frontend-static.prod.public.atl-paas.net/assets-brotli/jira-spa.0ef0264099832242467e.8.js:103:256711","name":"i","statusCode":404,"traceId":"1b3f7dcc96e80c12"},"buildKey":"JF-PROD-18395","logTime":"2020-08-13T20:07:58.153Z","browserName":"Chrome","browserVersion":"84.0"}

    etc

1 answer

0 votes
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 14, 2020

Hello Ivan,

Welcome to Atlassian Community!

Thank you for sharing the steps. 

Testing on my local site, I wasn't able to replicate the issue, so I would like to know more details.

Are you able to open this ticket directly on xxxxx.atlassian.net/browse/KEY-123? 

Since the link that you are clicking is related to a specific comment, in case you can view the ticket, is the comment there?

Is this issue happening with other people that have permission to view the ticket?

Is it happening to other tickets from the same project and from other projects that you have access to?

Regards,
Angélica

Ivan Trechekas August 14, 2020

I investigated what you asked.

> Are you able to open this ticket directly on xxxxx.atlassian.net/browse/KEY-123? 

No, We couldn't connect to that issue (404)


>  Since the link that you are clicking is related to a specific comment, in case you can view the ticket, is the comment there?

A direct link gets 404, link to specified comment - gets redirect loop. 

So, In Jira I have no permission to see this project (i think), but...*

> Is this issue happening with other people that have permission to view the ticket?

The person from the Service Desk has no issue at all. A direct link brings him to the ticket and a link with the comment to the specified comment.


> Is it happening to other tickets from the same project and from other projects that you have access to?

I don't see a project page for xxxxx.atlassian.net/browse/KEY. It's the Service Desk project.


*But... If I open the service desk link:
https://xxxx.atlassian.net/servicedesk/customer/portal/y/KEY-123?token=<some_big_token_here> - I can see the ticket and comments 


Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 18, 2020

Thank you for the details, Ivan.

It means that you have access to the project only as a Customer and not as an Agent. That's why you can access the ticket using the customer portal, but not through Jira.

There is a feature request suggesting improvements for that:

If you need to access the ticket internally, please talk to your site administrator for them to add a Service Desk license to your profile and add you to the Service Desk Team role in the project.

Ivan Trechekas August 18, 2020

I recommend changing the type of the ticket: from Suggestion to Bug, as we have 'unworking' functional for such links.

Thx. My goal was to clarify this situation and help to fix it in the next releases. If we have a ticket - it's ok for me.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events