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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira server - There is a below issue that we are currently facing in Jira in our backlog view

Jira Issue.JPG

1 answer

0 votes
Tuncay Senturk Community Leader Sep 02, 2021

Hello @tejashree avinash aringle 

You only cropped the beginning of the stack trace, however, it makes sense to include them all as they give us a chance to locate the root cause of the problem. Sometimes a plugin's code might cause such a problem as well as Jira itself. In this case, I only see GH (GreenHopper formerly Jira Agile) which is Jira Software.

If you can't see any suspicious plugin lines within the rest of the stack trace, you can raise a support ticket to Atlassian directly in your Jira instance.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events