JIRA Ticket not opening

In Our JIRA instance there are 3 tickets which not opening says "issue may have ben deleted or you might not have permission to see it", but i am a administrator i should be able to see it. I have done the JIRA integrity cheeking and problem remain same. what is the workaround for this ?

1 answer

0 vote

Check the permissions on the issues.  You will find your account probably does not have the rights to see it.  Or you've deleted it.

"Admin can see/do everything" is a terrible permissions model, and thankfully, one Atlassian do not do.  Just because you're an admin, you don't get to ignore all the security and permissions. 

If someone deleted, it cannot be shown in the issue filter but as seen in the screen it is showing. Is there any way to see the permission of those tickets, since it is not opening but other tickets in the same project are opening.

I'm sorry, I didn't understand that it was showing in search from the original question. If an issue is hidden from you by permissions, it will not show in searches either. So, there are now two possibilities, I think: 1) You are searching for issues with a user who can see it, then using a user who can NOT see it to visit the issue. I doubt this is the case, but just in case (and to help you understand permissions) The permissions for an issue are all handled by the permission scheme on the project, and the issue security scheme on the project too. You just need to read those to work out if you should be able to see the issue. 2) The issues have been deleted, and your index is corrupt. This would leave you in a state where the search is still reporting the issues because the index says they are there, but an error when trying to reach them. Try a full re-index. You should find the issues vanish from the search results afterwards.

i have done a full re-index but didn't fix the problem

Also i have checked no issue level security added and permission is there with permission scheme

Full re-index - the ne that locks jira while it runs?

Ok, then I have to suspect there's an addon breaking something somewhere. When you search for the issue, and then try to follow the "view issue" link from the search, what exactly does the application log file say? I expect there to be significant errors in there.

Log file contains search started 3.52AM 2016-01-12 03:50:16,100 http-bio-80-exec-1393 ERROR chandimai 230x150184x1 13hboho 172.25.12.43 /browse/GTP-5198 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:50:16,100 http-bio-80-exec-1393 ERROR chandimai 230x150184x1 13hboho 172.25.12.43 /browse/GTP-5198 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:52:24,332 http-bio-80-exec-1338 ERROR tevans 232x150307x2 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:52:24,332 http-bio-80-exec-1338 ERROR tevans 232x150307x2 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:52:29,823 http-bio-80-exec-1352 ERROR prasannak 232x150318x1 bfbm2n 172.25.123.8 /browse/MSS-2361 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:52:29,823 http-bio-80-exec-1352 ERROR prasannak 232x150318x1 bfbm2n 172.25.123.8 /browse/MSS-2361 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:53:35,343 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN tevans 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 03:53:35,733 http-bio-80-exec-1378 ERROR tevans 233x150424x2 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:53:35,733 http-bio-80-exec-1378 ERROR tevans 233x150424x2 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:53:41,692 http-bio-80-exec-1406 ERROR tevans 233x150437x4 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 03:53:41,692 http-bio-80-exec-1406 ERROR tevans 233x150437x4 3a0tp4 10.124.156.80 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED

I started another search and here are the log file details 4.14 AM started search you can see my search on log saying kwijerat as as username 2016-01-12 04:14:07,462 http-bio-80-exec-1399 ERROR warunas 254x151897x3 apm9c8 172.25.12.122 /browse/GTP-4463 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:14:07,462 http-bio-80-exec-1399 ERROR warunas 254x151897x3 apm9c8 172.25.12.122 /browse/GTP-4463 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:25,213 http-bio-80-exec-1338 ERROR prabasha 255x151983x5 reft3l 172.25.27.97 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:25,213 http-bio-80-exec-1338 ERROR prabasha 255x151983x5 reft3l 172.25.27.97 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:37,849 http-bio-80-exec-1408 ERROR prabasha 255x152026x9 reft3l 172.25.27.97 /browse/GTP-877 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:37,849 http-bio-80-exec-1408 ERROR prabasha 255x152026x9 reft3l 172.25.27.97 /browse/GTP-877 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:42,029 http-bio-80-exec-1400 ERROR rasikaw 255x152031x4 rtk1zs 172.25.65.45 /browse/MSS-426 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:42,029 http-bio-80-exec-1400 ERROR rasikaw 255x152031x4 rtk1zs 172.25.65.45 /browse/MSS-426 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:44,494 http-bio-80-exec-1411 ERROR juliand 255x152033x4 1qz2taq 172.25.35.111 /browse/MSS-2361 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:44,494 http-bio-80-exec-1411 ERROR juliand 255x152033x4 1qz2taq 172.25.35.111 /browse/MSS-2361 [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:51,343 http-bio-80-exec-1404 ERROR kwijerat 253x151889x3 19k5q4w 10.124.156.95 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:15:51,343 http-bio-80-exec-1404 ERROR kwijerat 253x151889x3 19k5q4w 10.124.156.95 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:16:11,872 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN akryukov 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,013 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN chathurig 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,200 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN dilanfe 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,371 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN juliand 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,496 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN drak 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,637 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN tharindae 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:12,871 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN ryauseye 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,011 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN rsameera 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,136 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN rwadhera 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,339 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN prasannak 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,463 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN lmoore0 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,604 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN nchehera 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,744 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN vkarpika 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:13,900 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN vsetsko 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:14,041 com.atlassian.mywork.client.reliability.DefaultUnreliableWorker:thread-1 WARN tpavlyuk 740x281x2 fsm1z6 10.104.156.118 /secure/CreateIssueDetails.jspa [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="http%3A%2F%2Flsegdocs.lseg.stockex.local"} 2016-01-12 04:16:14,103 http-bio-80-exec-1408 ERROR juliand 256x152106x3 1qz2taq 172.25.35.111 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED 2016-01-12 04:16:14,103 http-bio-80-exec-1408 ERROR juliand 256x152106x3 1qz2taq 172.25.35.111 /secure/AjaxIssueAction!default.jspa [jira.plugins.d.d] [Enhancer Plugin] EXPIRED

Right. Thought so. Go to Admin -> Manage add-ons and find the "JIRA Enhancer plugin". Remove it. Try again.

It is already expired, is there any impact of removing it to the JIRA server ? what is the use of it ?

If you remove it, it will stop erroring. JIRA Should ignore it. Worst case is we can just re-install it later. As for the usage, the question is what you installed it for! I don't actually know which "enhancer" add on it is, but you can have a look in "manage add-ons" to find out.

if it doesn't break the existing functionality of the JIRA server we are ok to remove the plugin ? i saw 119 modules of JIRA Enhancer plugin installed.

It won't break the core functionality and won't damage your data. But TEST it fully before you do it. Ideally in a test system with a copy of your data. If you must do it live, try disabling the add-on first, without removing it (then it's easy to re-enable later if that causes any issues)

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published 4 hours ago in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

26 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot