Issue When Moving JIRA Issue with Sub-task: Retain Field and Mandatory Fields Prompt

Question

Hello JIRA Community,

I'm encountering an issue when moving an issue from one issue type to another in JIRA, specifically from "Observation" to "Defect". Initially, when I moved the issue without any sub-tasks, the transition was smooth, and I didn't face any prompts for mandatory fields or the "Retain" field values option.

However, after I created a sub-task under the issue, and then attempted to move the parent issue to the "Defect" type again, I was prompted to fill out several mandatory fields and was presented with the "Retain" field values option. This wasn't the case when there was no sub-task involved.

Can anyone explain why this happens and how I can configure my workflow or field settings to avoid these prompts when moving issues with sub-tasks? Any advice on how to streamline this process would be greatly appreciated.

Screenscheme/Field configuration same for both issuetype.but when I create a new sub-task only facing the issue.

Thanks in advance for your help!

Lisa Forstberg_o85gu4 · Answer

Puzzeling !

If these fields are not needed in these projects at all I  would have tried to see if excluding the projects via field context would solve the popup problem during the move action.

I would also consult atlassian support to see if we can get an explanation to why these fields appear.

Best regards

Lisa

Tharunkumar B · Answer

Thanks @Lisa Forstberg

Eg:Field configuration/screen scheme same for subtask,observation,defect issuetype and also move issue within Project itself

Lisa Forstberg_o85gu4 · Answer

Hi @Tharunkumar B ,

As you are not allowed to separate a parent and a subtask via the move, every move will automatically also move the subtasks. Perhaps you are faced with mandatory fields for the subtask when you are moving a parent/subtask.

I would check

* the field configuration for the respective issue types in the target project that you are moving the tickets too. Any trace of these fields being required?
* the workflows of the respective issue types in the target project - specifically look at the create issue transition for any validations
* Are these fields present on any of the issues screens in the target project
* Check these fields - what contexts do they have?

I think I have seen this behaviour in other environments too  but I haven't investigated it fully yet.

best of luck

Lisa