Can we make field mandatory only on move screen

[Gaurav Arora]

Can I make custom fields mandatory only on the move screen of an Issue type?

We are using the same workflow and screens for an issue type, say A in all the projects. When a user moves the ticket of issue type A to another project with the same issue type A, can I make a custom field mandatory on the move screen only and without making the field mandatory on other screens?

I have tried doing it with the field configuration scheme. Made the required field mandatory(Required) and it was working fine on the move screen but this field is also available on other screens( mainly transition screens ). So, when I am doing the transition, even if I don't want to enter any data, the field is mandatory. Also, I don't want any changes to the field's value if anyone's going to suggest writing a script runner behaviour.

I have made it possible for Create Screen to work out well. Since I don't need it on the create screen so I configured a script runner behaviour giving a default value to the field and making it hidden. Then, I am clearing the field's value through a post-function. This post-function is situated above the Create Issue post-function in the create transition so nothing gets logged in the issue history.

Does anybody have any Idea?

[Nic Brough -Adaptavist- · Accepted solution]

No.

The mandatory flag is not set by screen, it is done by issue type and project (in the field configuration).  The move function applies this flag when the target issue type needs it in order to avoid the data becoming inconsistent.

Validators apply only to transitions.  Edit and move are not transitions, so they don't apply.

The question you have to ask is "why?"  Why do you think you need this?