Subtasks issue keys are NOT searchable when moving a parent between projects

[Julian Sanchez]

I moved issues from project A to project B and I get an “Issue Does not Exist” when trying to acces an issue key of project A.

Normally when moving issues between projects the old issue key is still searchable. I found out that is true for parent issues but not for subtasks.

Is there is a solution to this?

I am using Jira v6.1

Thank you!

[Lucy Corral]

Thanks much Jose. It sure seems like a JIRA version issue now. We will follow up with support

Regards,

[Jose M.]

Hola Julian, hola Lucy.

I've tested it, created an issue and a sub-task, afterwards moved both to another project and used Quick Search to search for the issues. It works without problems.

Your problem is surprising anyway, but probably you will have to contact the Jira support.

But you could check the Administration Advanced Settings regarding
jira.projectkey.pattern
A regular expression that defines a valid project key.

This entry causes problems if not correct.

[Lucy Corral]

Thanks Jose for you quick answer.

After further investigation, we found that the issue is present in two systems that are still using JIRA 6.1.1 and have the Agile plugin installed. The issue is NOT present in a system with version 6.2.6 with no Agile.

Could you let us know whether your setup is using Agile?

I looked through the Release Notes of all versions from 6.1.1 to 6.2.6 and there is no task that specifically talks about searching of moved subtasks.

Regards,

[Jose M.]

Hi Lucy. Yes, Jira v6.1.5 and Agile v6.3.6.1 while testing the behaviour.

[Lucy Corral]

Hi Jose, I can answer the question. Yes, search works fines with not-moved sub-tasks

[Jose M.]

OK, but in general: Does the search work with not moved sub-tasks?

[Julian Sanchez]

Yes, the sub-tasks were moved with the parent issue and when searching and a search for the previous sub-task key returns an “issue does not exist or you don’t have access…” error.

I moved 4 issues that had sub-tasks, all sub-tasks exhibit the same behavior.

[Julian Sanchez]

Yes, the sub-tasks were moved with the parent issue and when searching and a search for the previous sub-task key returns an “issue does not exist or you don’t have access…” error.

I moved 4 issues that had sub-tasks, all sub-tasks exhibit the same behavior.

[Jose M.]

So the sub-task was moved with the parent and you can"t search the previous sub-task key? Sounds strange. Does it work with other sub-tasks?