nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error 500 when moving issue in next-gen project

Szymon Sobczak_ynddyq

I'm getting Error 500 when I try to move issue from one next-gen project to another.

I've tried with different issues (open, closed, stories, tasks) and I'm always getting the same "Error 500".

Update: this also happens when I try to use "Move" function to convert a Story to an Epic within the same project. It happens in newly created projects too.

This is the screen I'm using to move the issue, nothing complicated:

Screen Shot 2020-06-27 at 8.41.57 PM.png

Any ideas how to debug this?

Accepted answers

All comments

John Funk

Hi @Szymon Sobczak - How many issues are you moving?

Szymon Sobczak_ynddyq

The error happens when I try with one issue as well as in bulk. I've tried multiple different issues one-by-one (open, closed etc.) but I get the error every single time.

John Funk

Since Next-gen projects are very independent of each other, make sure that anything you have added to the source project is also in the target/destination project. That includes custom fields you created, columns, labels, etc.

The first thing I would look for is the status of the card you moving from and to so you can verify if the status is the same. Though a Move should recognize that.

Szymon Sobczak_ynddyq

Hi @John Funk , thanks again for helping with this! I've removed all custom fields from both projects, deleted all custim issue types and added stage transitions from "All statuses" to every single status, but that didn't help

I've also tried exporting the issues to CSV and importing it in the second project, but that doesn't work because of another (confirmed) bug, described here: https://community.atlassian.com/t5/Jira-Software-questions/Cannot-import-subtasks-bug-with-quot-Issue-Type-quot-during/qaq-p/1417981.

Do you have any ideas on what else I could try?

Petter Gonçalves

Hello @Szymon Sobczak

I believe you are being impacted by the bug below, where the creation of a new component during the move option can cause the 500 error:

Adding a new component when moving issue returns a 500 error

To work around the problem, click the back arrow twice of your browser when you get the 500 error to get back to the component screen. There, you will see the component is already created so you can follow-up the Move client to finish the move.

Can you confirm if that worked for you?

Also, I suggest voting and watching the bug to increase its priority and also receive notifications about its fix implementation.

Szymon Sobczak_ynddyq

Hi @Petter Gonçalves , thank you for looking into this!

Unfortunately I think this is something different. I've tried on an issue with no components. There was no screen to select them. I see "Error 500" after the first step in conversion process, so after clicking "back" twice I was out of the wizzard and back on the issue screen.

I see this error converting issues from Classic to Next Gen project, but also Next Gen to Next Gen and even using the "move" option to convert a Story to an Epic within the same project.

The steps to reproduce are:

1) on an issue screen click "move"

2) the step on the screenshot below

Screen Shot 2020-07-01 at 10.00.33 PM.png

3) clicking "Next" gives me error 500 - even in this exact configuration, changing Zadanie (it means "Task" in Polish) to Epic, within the same project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

next-gen

bug

error

move