How to force the assignee in some of the issue types

Question

Hi team,

We have a request from the manager, he found that some of the tickets were resolved/closed/canceled/done without an assignee, which caused some issues with the reporting. They would like to make sure that when the ticket is resolved/closed/canceled, the assignee field must have someone's name there.

My original thought was to use the automation rule:

Trigger: When transition ticket to resolved/closed/canceled/done etc.

Condition: Assignee is empty

If/else block: to match different destination status( different issue types may have different original steps and destination step.

Action: Transition to the specific status

After finishing this automation, I encountered some issues:

1. the automation rule is quite long based on different status on different issue types

2. if the resolved/canceled/closed/done status has no transition to the previous staus, then the automation rule will not run properly. eg. the canceled status has no transition to waiting for support, so it can't perform.

Any ideas or suggestions? Thanks.

Cristiano Alves -Appfire- · Answer

Hi @Lance Li ,

Unfortunately the assignee post-function in Jira Data Center is quite limited.

On the software our team works,  Jira Misc Workflow Extension (JMWE), you should be able to do expand this option, just add the function that will become available. Here is the configuration screen of said function:

You are able to assign it to either the current user, the reporter, lead, last commented user and so on, while also being able to set up custom conditions.

If you need something like field required validator are also available from it, so you should also be able to set the assignee field as mandatory before closing the ticket.

Please contact our support if you have any other questions about this validator, or JMWE in general.

Regards.

Walter Buggenhout · Answer

Right, you are on Data Center 😅 ...

Yes indeed, this does not come out of the box there and even Atlassian recommends using an external workflow app from the marketplace to extend this capability, as you can read in the official support documentation.

If you need solid workflow configuration on Jira DC, having such a workflow extension added is actually a must. So I strongly recommend this.

If that is not an option, you can still apply the other suggestion using a postfunction to set the assignee automatically. You can also do this earlier on in the process, e.g. when someone moves a ticket to In Progress. That will also drastically reduce the chance of having unassigned tickets lying around.

Lance Li_fvd6if · Answer

Hi @Walter Buggenhout

Thank you very much for the reply. Would you mind elaborating on the send approach you mentioned? I would like to know how I can achieve it in our workflows.

When checking the validator on a transition, I can't find "a field required validator".