Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,391
Community Members
 
Community Events
176
Community Groups

Automation - Custom field value trigger does not trigger

We have a read-only (for the issue UI) customfield that's added and changed by an app.

cf-app.png

The following automation trigger never fires.

cf-trigger.png

The value of the 'Customer Sentiment' field is changed by the app's back-end after AI sentiment analysis, which runs async to any issue transitions.

Documentation states that "The rule will run when a field value is changed. All system and custom fields are supported by this trigger."

This is not the case.

I would like some advice on how to get this trigger to work.

Thanks for your help, 

Best Ulrich

1 comment

Hi @Ulrich Kuhnhardt _IzymesCo_ ,

We're using the app-generated custom field as a trigger as well in many automations.

Here is an example of the field and how it looks like in Jira 👇

Screenshot 2022-03-14 at 09.12.37.png

It's a numeric field that stores Priority Score for our Foxly app. But we also have dropdown custom field types that are also working with Automation.

Just to mention, all values of these fields are stored in properties too, so I think we do have a very similar setup.

 

A few questions to help me understand a bit more:

1. What field type is your field? Numeric?

2. Is the value of the field actually updated? Can you see that in Issue history?

3. Automation doesn't get triggered at all?

 

Thank you!

Thanks Nikki! 

I checked the foxly descriptor and added a simple automation on the priority score. Works like a charm! Thanks for your help!

Happy it helped 👏 

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events