You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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:
*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.