Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Service Management automation tool for custom field not reading empty

I have a custom field list of teams (i'll call it CFTeam)-- I am automating it based on the reporters field department it is auto assigned a CFTeam for issues created on the portal. Then it is sent to that team's queue.

If the issue is created inside JIRA then the agent can populate the CFteam field.

The rule is written:

At issue creation:

if CFTeam is not empty then create the issue

If CFTeam is empty then lookup reporter's department and CFTeam = (corresponding choice from CF Team list)

------

the audit log says it passes criteria one no changes... so it is not reading the CFTeam as "none."

Original creation had department auto assignment first and agent choice -- but then the reporter's department overwrites the Agent' choice and it ends up in the wrong queue.

----

We are currently on a trial basis for this tool, could that be impacting the logic?

1 answer

By default, rules run as the person who created the project. Alternatively, you can run rules as the person who triggers the rule. For example, if a rule responds to a customer, then you might want the comment to be from the agent who is working on the request, not from the person who created the project. In this case, you would want to set the Run rule as to User who triggered the rule. Make sure the person you choose has permission to complete all the actions taken by the rule.

Triggered by other rules: By default, rules can trigger other rules. In some cases, you might need to disable this to prevent two rules from triggering each other infinitely.

To change the default Run as user, go to Automation > Change default event user. Make sure the person you choose has permission to perform all the actions that you might try to automate in all your rules.

 

DGCustomerFirst

@John Mett Those settings are not affecting the rule; The question is why the project automation rule is not reading "Empty" Status of the field.  If there is no selection from the field have an empty value.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

269 views 13 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you