How can I require that a component is defined for every new issue entered or moved into a project?

[Lauren Larsson]

In my on demand install, I have a project which requires component to be entered for every new issue created. I am currently migrating issues into a new project and during the move, the system is asking me which component from the new project to apply to each parent task. However, the child tasks are arriving in the new project without an associated component. Also, we would like for it to be generally required to give any new issue a component. Thank you!

[Norman Abramovitz · Accepted solution]

Please search the bug resporting site and if the bug does not exist already, please report it. It would help to put the bug report url here, so other people can follow when Atlassian fixes this issue.

[Lauren Larsson]

See screenshot below. Under field config in the project in question, it says that component is required in all issue types, including subtasks.

Think I may have found a bug.

Edit: I have figured it out: There IS a bug when you use "Move" to move an issue that has subtasks, but not when you use "bulk move." I'll be using bulk move from now on, but I think Atlassian should take a look at fixing this.

Thank you for your help!

[Norman Abramovitz]

I would check your field configuration schema associated with your subtask issue types. The field configuration schema is the place where the required setting should be located.

[Lauren Larsson]

Maybe not for subtasks, but the subtasks do have component assigned before the move. I would like to require component for subtasks too. Is it possible?

[Norman Abramovitz]

Are you sure your subtasks has the component field marked as required?

[Lauren Larsson]

Maybe not for subtasks, but the subtasks do have component assigned before the move. I would like to require component for subtasks too. Is it possible?