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,556,422
Community Members
 
Community Events
184
Community Groups

Project automation: create rule for comments from portal

I am trying to create a rule, which transitions my issue when a comment is created. This basically works fine. 

But when I am trying to add a condition, I am failing: 

I want my issue only to transition, if the comment is created in the portal and not in the Jira backend. 

I know that there are certain properties and that it is possible to set them with the "advanced compare condition" but I am not able to find out the right parameters. 

So I have two questions: 

1.) how to write my condition, so that my rule is only triggered my comments created in the service desk portal? 

2.) does there exist a list with all field properties and an explanation for what they are used? 

thanks for your highly apreacciated help! 

(I am project administrator, but not a Jira administrator with global permissions) 

1 answer

0 votes
Jan-Hendrik Spieth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 31, 2023

Welcome, @systemlos :-)

Have you also tried setting a "User condition"? I think this might work, using some group, role, organization or so, as condition then.

About "all field properties" - the documentation for smart values might be a place to start?

Hope this helps...

thanks for reaching out to me.

everybody is allowed to raise requests. The user condition would not be perfect, because if a user is an service desk customer and an agent at the same time, a comment in Jira would be interpreted like a comment from portal. Best would be a certain property, where I can declare,  that the comment had to be raised by portal. 

thank you for the link :)

these IF conditions will do as a workarround for now: 

ifconditions.PNG

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events