Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,463,539
Community Members
 
Community Events
176
Community Groups

Since upgrade to build 5.5.0 we can no longer create issues from queue or update the status

Edited
Toby Pittman
Toby Pittman Dec 31, 2022

Since upgrading from on-prem Jira Service Management build 5.0.0 to on-prem Jira Service Management build 5.5.0 we can no longer create issues from within the queue or update the status of issues or move any issues through any workflows while in the queues.

Any help anyone can provide would be great… perhaps Atlassian support will see this. This is causing major issues with our environment.

Thank you.

Toby

 

 

Answer
Watch
Like Be the first to like this
141 views

1 answer

0 votes
Ismael Jimoh
Ismael Jimoh Community Leader Dec 31, 2022

Hi @Toby Pittman 

I will start by reviewing the Jira logs to track of any necessary packages didn’t Startup following the upgrade.

You can achieve this by generating a support zip.

With the information from the logs, you could decide to restart the server or based on the error you see try and fix the root cause.

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
DEPLOYMENT TYPE
SERVER
VERSION
5.5.0
TAGS

Atlassian Community Events

See all events