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; } } }

Cannot move issues from one project to another (due to recent changes by another user?)

Angelo_Hulshout

NOTE 2019-01-11: Bug fixed, problem solved. https://jira.atlassian.com/browse/JRACLOUD-71354

When performing a bulk move from one project to another, I get the following error message after the Confirmation step:

At least one of the issues you are trying to move has been recently updated by another user (T6-1160). Please cancel and start again.

Does any one have a clue as to what may be causing this and how to overcome the problem, since no issues are moved. Searching the web and knowledge base doesn't bring up anything at all.

Thanks,

Angelo

Accepted answers

Angelo_Hulshout

Update:

This is a bug, reported on JIRACLOUD now. See bug description and suggested work around here, and please vote for it.

====

First feedback from Atalassian: this fails for stories that have subtasks. They're investigating further, also because the problem didn't occur before mid December, so it might be related to a software update.

All comments

shetty

Can you share Screenshot of error

Angelo_Hulshout

The problem is the same for all Stories I try to move. When moving in bulk, the erorr simply appears for the first story in the list.

Jason DePietropaolo

I am having same exact error when trying to move a card with subtasks to another project.

At least one of the issues you are trying to move has been recently updated by another user (PS-1367). Please cancel and start again.

hanh1985

I have the same error. This can be resolved by converting all sub-tasks to tasks...

Sven Schmid

Same here.

Sven Schmid

Why is this the accepted answer?

Angelo_Hulshout

Atlassian is on it. When I get a solution I'll post it here as well.

Angelo_Hulshout

One click too many ;-) It's not anymore.

Angelo_Hulshout

Update:

This is a bug, reported on JIRACLOUD now. See bug description and suggested work around here, and please vote for it.

====

Britney Miller

Has the work around worked for you? I am getting an error when switching parent to a ticket in another project.

Jason DePietropaolo

converted sub tasks to tasks and then was able to move card. Not perfect solution but it worked for what I needed it to do.

Angelo_Hulshout

Trying the workaround today, Britney, but I think the idea is that you move all the tickets before trying to re-create the parent relationships.

I'm sure it works, Jason, but it's cumbersome in our case (35 stories, 130+ subtasks), and the problem didn't exist until end of last year.

EDIT: it's unworkable in our case. Getting Atlassian in to find another solution.

Jamie Elliott_l3c67k

Following this chain as I'm also affected by this bug!

tina_ash

I would like to report that we are having this issue as well.

Navneet Dhami

Hi, Is there an ETA provided for this issue ?

Zee_l2v45l

We are having the same issue.

Tim Heath

My team is having the same issue as well.

Tim Heath

Just confirmed that this is now fixed!!!

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software