Unable to see the issue types from down while moving the tickets from one project to another proejct
Asked by Lakshmi S:

Hi Team,

While we are moving the jira ticket from one project to another, not able to see the issue types from the target project, when we entered the name its taking. Please find the attached screenshots for your reference.

![move1.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/161576i315431FE5B298FBB/image-size/large?v=v2&px=999 "move1.PNG")![move2.png](https://community.atlassian.com/t5/image/serverpage/image-id/161577iA803E508FED82752/image-size/large?v=v2&px=999 "move2.png")

Thanks!


Answers:
author: Nic Brough -Adaptavist-
body: The two screenshots look like they are from two separate, differently configured, systems (like a production system and a test system that was a copy of production)

Could you confirm that this is the case? Or explain what you are doing differently in order to get two totally different screenshots?

Assuming it is two different systems, the answer is simple - the issue type scheme for project BIRO in one of the two systems is different. It has to offer you a different list.

comments: author: Lakshmi S
body: Hi [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) ,

No, both are from same production and same moving wizard. In the first screenshot i wasn't able to see the Task issue type, but when i typed in the second screenshot, i was able to see the task issue, ie the target issue type to move BO to BIRO project.


author: Nic Brough -Adaptavist-
body: Hmm. I've managed to replicate that, and it looks like a bug.

I'm going to guess that you get an error if you actually try to commit to this change, because what I think is happening is the "task" is initially hidden from the list because it's not a valid choice, but the typing lets you specify it.

Could you confirm what happens when you select next and follow it through the move process?


author: Lakshmi S
body: Hi [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) ,

I was able to move the ticket successfully.

![move3.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/161770i8515FCC5512EA30C/image-size/large?v=v2&px=999 "move3.PNG")


author: Nic Brough -Adaptavist-
body: Ahh, hang on, you've changed project there as well. That makes perfect sense - the original project has one list of valid issue types, the new one another list. That's why the options change - you're moving across projects.


author: Kishan Sharma
body: Hi [@Lakshmi S](/t5/user/viewprofilepage/user-id/11952)

If your issue is a custom issue type that does not exist in your New project, you must select a new issue type. You can also choose to arbitrarily change the issue type OR can add the issue types first in the New project and then move the issues from your Current Project to New.

comments: author: Lakshmi S
body: Hi [@Kishan Sharma](/t5/user/viewprofilepage/user-id/554991) ,

Thank you for the quick response, Its not related to custom issue type or new issue type. When moving a ticket from the one project to another project on the move screen the drop down for the Task Type of the destination project doesn't show all task. Only the first is visible. You're able to manually type in the name of the task if you know it but you can't select it from the drop down.


Tags: confluence-server

jira-server

server