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,555,326
Community Members
 
Community Events
184
Community Groups

Cant change story to task

Edited
Marko Sahan
Marko Sahan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
May 10, 2023

After creating a ticket, I wanted to change the story type to a task type. In the end, after confirming all changes, I got the error with a log reference a5f86ab6-28ca-406f-a09a-dbd3eef5e04f

The issue occurred yesterday. At least 4 more colleagues faced with the same problem

 

Screenshot 2023-05-10 at 10.29.51.pngScreenshot 2023-05-10 at 10.29.58.png

Answer
Watch
Like Be the first to like this
97 views

1 answer

0 votes
James Havelock
James Havelock
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
May 10, 2023

Recommend you first get your project admin to try the same task. Then at least, if they succeed, you know it is likely to be a permission based issue - and if not, then you can try in a different project in the same Jira instance to see where to look for the best next troubleshooting step.

View More Comments
Marko Sahan
Marko Sahan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
May 10, 2023

The issue occurred across different tickets and different projects. I listed my issue as the example. Previously there was no need to be an admin to change the ticket type and I did it freely. 

Like
Nic Brough -Adaptavist-
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.
Become a leader
May 10, 2023

This is a back-end error message, something went wrong on the server running your instance. 

It may be related to permissions, but it won't be that your people don't have the right permissions.  If it were, you would not be offered the option to move the issue to the new type.

This needs to be raised as a problem with Atlassian - report it on https://support.atlassian.com/contact

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events

See all events