Is there any way make comment field mandatory after changing assignee

Question

Hello Folks,

I just need to make it a way to mandatory the comment if someone changes assignee on edit issue screen without any Plugin or third-party marketplace Apps.
Also, I already restrict this in workflow transition means if someone changing assignee while transitioning work item, comment is mandatory.

If someone is ever configured it or know how to do it, will help me lot.

Dominik Kaźmierski · Answer

Hello Akshata Mali!
There is one thing that comes to my mind in this case.
I would restrict assignee change using workflow property jira.permission.assignable and then make it possible only via transition screen.
In order to make it work You would need to add new loop transition ('from statuses: any status' -> 'to status: to itself').

Creating that transition makes it available to use by clicking on automation button, next to the status button.

Let me know if you have any questions.

Arkadiusz Wroblewski · Answer

Hello @Akshata Mali

Only Partly, theres Feature Request adressing exactly your problem. [JRACLOUD-82196] Make comment field mandatory when changing assignee - Create and track feature requests for Atlassian products.

How to set up the "Comments" field as mandatory when changing fields such as Priority | Jira and Jira Service Management | Atlassian Support

You can't enforce a comment on inline Assignee edits natively, Jira validators only run during workflow transitions (doing this directly on the field requires a Marketplace app).

The best native workaround is creating a self-transition (e.g., "Reassign") with a required comment screen, while removing the Assignee field from your standard Edit screen.

Best,

Arek🤠

Tomislav Tobijas · Answer

Hi @Akshata Mali ,

Well... On edit screen you won't be able to build this. You could either use self-reflecting or global transition. For example, build a specific transition (e.g., "Update Assignee") that uses a screen containing both the Assignee and Comment fields and make them mandatory with workflow validations.

I'd rather go with removing the Assignee field from edit screen so the field is not editable and then build some kind of workaround. 👀

Maybe you could build some kind of Forge app but that would require some effort, probably and I'm not sure how 'optimal' the performance of Jira would be then 😕

Cheers,
Tobi