Jira Move operation - cannot move because field is required

[Pakorn_Srikeow]

Hello --

In Issue 1, I am unable to move from "Inside Only" to "Bug" because it says that the "Actually Seen Version/s" field is required, but I am unable to edit it in the screen, even as a Jira admin. In this issue, it does have a sub-task tied to it.

In Issue 2, I AM able to move from "Inside Only" to "Bug", and when it asks me to update fields, I can type in the "Actually Seen Version/s" field to whatever I'd like. Issue 2 does NOT have a sub-task associated with it.

My question, what am I missing in Issue 1 vs Issue 2, besides the sub-task? How can I go about fixing this? Thanks. 

[Pakorn_Srikeow]

The issue ended up being a bit more complicated. 

When "moving" Jira linked-issues, it actually defaults to "retain" data from one issue to the other. In Issue 1 above, it did not have the "Actually Seen Versions" field required, or even showing, and therefore, when converting to "Bug" which required this field, it kept throwing an error that the field was required without an easy way to fix it. This is because in Issue 1, it is "null" and it was retaining the null value into the new issue type that required data to be in that field. 

Based on previous documentation, you can do short-term workarounds, and unlink the sub-task, convert it to an issue, convert Issue 1 to "Bug", convert issue back to a sub-task, and then link the ticket.

My solution will probably end up being to make the Custom field in question visible, so that it can capture data. Even though the error will still persist, at least they are able to fix it. 

Thanks again @Nic Brough -Adaptavist-

[Nic Brough -Adaptavist-]

This suggests that issue 1 and 2 are of different types and/or project, and have different "edit" screens.  Check the issue type screen scheme for issue 1 contains the field in the edit screen.

[Pakorn_Srikeow]

Thanks Nic! I'll check that out and report back.
PS: I met you at the US Atlassian Summit last year, and I love that you're always helping out on the board.