Opening a ticket from gadgets redirecting the tickets to a dead link?

Vineet Kumar April 21, 2016

Hi All, I am facing this issue from a long time, Whenever i try to open a JIRA ticket from the gadgets,

Image2.png,

it redirects me to a dead link as seen below

Image1.png

 

and also, it adds '/i/#' to the URL. This issue only appears on IE and i cannot ignore that as most of the employees are using IE in our organization. Is there any permanent solution for that, Is IE not fully compatible with Jira? The version of IE i am using is 11.

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2016

That's an interesting one.  There's several things it could be, so some quick questions

  • In your first screenshot, could you hover the cursor over the connectall-9 link in the gadget and see what the url presented there actually is?  Or, right click it and select "copy link" and paste it into notepad or a text editor to see what it is.  The question is "does the link url contain the extra /i/# ?"
  • As an admin, could you have a quick look at the list of "user installed add-ons" under "manage add-ons"?  Are there any in there that mention tracking or analytics ?
  • Are you running this JIRA behind a web server such as Apache, IIS or nginx?  If so, which one?
  • What is the "base url" of your system?  (You don't need to tell us, just check that it is just what you have obscured in your second screenshot - it does not contain the extra /i/# bit)
Vineet Kumar April 22, 2016

Thanks for the response Nic, please find the results

  • The url which is hovering is https://[BaseUrl]/browse/CONNECTALL-9, but when i clicked on chrome it went fine but in IE, ticket appeared for a second and then it redirected to the url with /i/# in it and became dead.
  • Yes, there are 2, One is Time Tracking and other is under Agile Card.
  • We are running Jira over TomCat.
  • Base url doesn't have these characters. 

I jusr found that, i can't even go to issue navigator in IE, it is also going to the dead link with the url, http://[Base URL]/i/#ssues/

Thanks

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2016

Ok, that rules out a lot of possible culprits, which is great.

When you say you're running JIRA over Tomcat though, does that mean it's just Tomcat?  There's no proxy at all?  Your url is something like http://ourserver:8080/jira ?

One other test - could you clear your cookies in IE and retry it?  Does the #i reappear in landing urls as soon as you click connectall-9 ?

Vineet Kumar April 22, 2016

I mean, we are running JIRA over the tomcat which comes with the JIRA installation, i am not sure  about the proxy, it is like https://abc.def.ghi./secure/Dashboard.jspa. (without the port in it).

 

I have cleared the cookies but it is still there, this is what happening.

URL 1: https://[base url]/browse/CONNECTALL-9 (this url is coming for 2 seconds and the ticket is appearing at 3rd second the url is automaticaly changing to the below one)

URL 2: https://[base url]/i/#browse/CONNECTALL-9

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2016

Ok, some more thoughts:

I think you definitely need to look at the possibility of a proxy, because there are ways a proxy could do that (and it's the most common way to drop the port number from a url)

It's very odd that the url is correct and then gets rewritten - that sounds like something odd is happening on the browser side rather than the server, but I don't know how you'd do it (especially if it's not happening with other browsers).  Is your IE customised in any way?

Lastly, could you take a look at the raw html of the page - is there any javascript that could be messing with the url?  Or redirect type stuff?

Sadly, I swear I've seen this once before, and I can't remember why, or even find the reference to it!

Suggest an answer

Log in or Sign up to answer