Loading JIRA Dashboard will go to Google Search

[doradoliz]

Hello,

Is anybody encountering the same issue?

When I try refresh the page (place the cursor in the address field and Enter)

It goes to google search automatically.

[Nic Brough -Adaptavist-]

Also, remove the "? select page ID" part of the url you are giving it - that looks wrong to me, so your browser is running off to search.

[Ravi Varma]

Hi @Nic Brough -Adaptavist-,

• For Cloud instances, the JIRA dashboard url does not contain selectPageId param. I agree with you in this case.
• For Server instances, the JIRA dashboard url contains selectPageId param. Looks like @doradoliz is working on server instance.

Regards,

Ravi Varma

[Nic Brough -Adaptavist-]

I know that, but with the parameters, the dashboard could be loading something iffy and it's going directly to a page that may not be accessible and/or require log in.

I'm asking to drop it because it's a poor thing to test with.  We need to see what the base url does.

[Ravi Varma]

Hi @doradoliz,

Your system is not able to resolve the JIRA server address (You have blurred the server address in the image).

Please speak to your system/network administrator to make sure that the server address is valid. 

Regards,

Ravi Varma

[doradoliz]

@Ravi Varma The JIRA link is correct

I think I found the issue

Notice in the below it can open the Dashboard

 

Select a panel and maximize.

It adds "#Two-Dimensional-Filter-Statistics/18749"

 

Then click Restore but it still has # in it. Press Enter from Address bar

And it went directly to google search

[doradoliz]

@Nic Brough -Adaptavist- have you checked the above issue?

[Nic Brough -Adaptavist-]

Yep.  Your system is not able to resolve the JIRA server address.

[doradoliz]

@Nic Brough -Adaptavist- I don't this is our network issue though. 

[Nic Brough -Adaptavist-]

It might not be the network, it might be the client machine (i.e. the browser).  But whatever it is, it's not a Jira problem, it's that your machine is not resolving the url to the right place and the browser is taking it as you wanting to search instead of to the url.  It's happening before Jira is reached.