Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can't open issue after comment manipulation

One of my agents changed the visibility of one comment from external to internal, and another added an internal comment in that issue. Afterwards, we are no longer able to open that issue. I can find it when searching for it by key or all issues in that project. When I click it I get an error message to the effect of "[Key] cannot be opened. It might be removed or you do not have the permission to view it.". On opening the next issue in the list and selecting the arrow for next issue, I get "Issue cannot be shown right now, this might be a network- or application problem. Try reloading". On reload, I get 502 - Web server received an invalid response while acting as a gateway or proxy server.

My agent is in the appropriate group for the project, and can work on other issues just fine. I am in the jira-administrators group, and can also view other issues in the project.

What I tried so far:

But the issue security scheme seems to be OK, and atlassian-jira.log does not show anything obvious regarding status properties.

But the SQL to verify the problem gives a clean result.

Null value in the created column of the fileattachment table? No, attached SQL gives nothing.

Finding the issue via the jiraissue table in the database shows it as being similar to other, working, issues. In the jiraaction table no comment for this issue stands out as different.

Cloning the issue gives me a 502 error, but the service desk team for the project got an email about a new issue being created by me. The new issue shows the same symptoms as the original.

The log scan shows But we are able to create new issues without problem and server.xml is set properly.

Log scan also shows Connection reset while accessing database, but the date does not match.

Jira service desk 4.5.0-REL-0034

Jira 8.5.1

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

2,227 views 28 39
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you