Notification for employee when organization = empty

[Jeremy]

Hi, I want to make the field 'organization' important in my Jira Service Management project.

When the employee doesn't fill in an organization, he needs to get an email with an alert of it.

I can make an automation-rule for it but I don't want the customer to be involved too when they don't fill out an organization. How can I fix this because I use an 'initiator' now.

[Els Bassant · Accepted solution]

Hi Jeremy, 

This can be done with an automation by combining some conditions.

If you are using automation, you need to add a user condition to filter out only issues that were created by your employees. I've used the standard "jira-servicemanagement-users-yoursitenamehere" in the example, but you'll have to check for your use case which user group(s) would best work here.

Though it might be even better if you can make the organisations field mandatory when creating the issue. I don't know whether this is feasible in your case.

[Bert van Dijk _TMC_nl_]

Hi @Jeremy ,

Please use a filter subscription for this.

https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-3-of-4

[Jeremy]

Yes but what is the JQL then? I only want the notification for the one who makes the issue (employee) and not the customer in the portal.

[Bert van Dijk _TMC_nl_]

Hi @Jeremy ,

Sorry, I didn't test it before, but indeed, it isn't possible.

https://jira.atlassian.com/browse/JSDCLOUD-9394

Even this suggestion is closed to no activity. Maybe create a new suggestion (or clone this one)

[Els Bassant]

Hi Bert, 

Are you sure about this? Because "Organisations = EMPTY" works for me on both DataCenter and Cloud and gives me the results that I expect.

So your initial idea of a subscription filter works. "Organisations = EMPTY AND creator in membersOf("jira-servicemanagement-users*")" should give a list of all issues created by service desk agents where the Organisations field is empty.

If you want send a personalised list to each agent you probably have to double up on the creator clause, so it becomes:

• creator is CurrentUser() AND creator in membersOf("jira-servicemanagement-users*") AND Organisations = EMPTY.

*use the appropriate user group for your own Jira instance, of course.

The linked request is specifically related filtering for SLAs and Reports, which react slightly different from the issue search.