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

[Angelo_Hulshout · Accepted solution]

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.

[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.

[Angelo_Hulshout]

And don't forget to vote up the ticket, please!

[Angelo_Hulshout]

We work around the problem temporarily by having stories from two projects on the sprints of one project and making both visible on the Board. This can be done by using a board filter like

project in (P1, P2)

instead of the standard

project = P1

Also Atlassian has raised the prio of the ticket to HIGH, a real fix that allows the move again (and kills the bug) should be available shortly. 

[Angelo_Hulshout]

Ticket has highest prio at Atlassian now, it might actually get fixed over the weekend :-o

[Angelo_Hulshout]

The issue was resolved this afternoon. Should be working as before now - at least it does for us.

https://jira.atlassian.com/browse/JRACLOUD-71354

[Tim Heath]

Just confirmed that this is now fixed!!!

[tina_ash]

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

[Zee]

We are having the same issue. 

[Tim Heath]

My team is having the same issue as well.

[Sven Schmid]

Same here.

[Angelo_Hulshout]

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

[Jamie Elliott]

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

[Navneet Dhami]

Hi, Is there an ETA provided for this issue ?

[Angelo_Hulshout]

[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...

[Angelo_Hulshout]

That is no solution - we’re not going to ruin our whole project structure for this....

[Britney Miller]

I am having the same issue as well. Stories without sub-tasks move no problem but those with sub-tasks get the 'recently updated' error.

[Angelo_Hulshout]

See my answer below.

[shetty]

Can you share Screenshot of error

[Sven Schmid]

Why is this the accepted answer?

[Angelo_Hulshout]

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