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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Workflow automation - Transition To/From waiting for customer not triggered by adding an internal no

I've created a workflow from scratch and am looking to replicate the standard workflow feature which changes the status to waiting for customer when a reply is sent to the customer and back to waiting for support when the customer replies.

Screen Shot 2021-11-04 at 3.04.49 pm.png

In my case i want to transition back to in progress.

The rule above works well but how can it be adjusted so it is NOT triggered by adding an internal note?

2 answers

1 accepted

3 votes
Answer accepted

Hi Scott,

If I have understood this correctly, you want the issue reporter to comment public to the client and it change to in progress? just not on internal notes?

If so, you should just need to add additional criteria into your automation workflow, on the "If"

Something like this:

[This is an additional If condition of, "advanced compare condition"]

eg compare values.PNG

Eg Workflow.PNG

This seems to work in my test environment.

Thanks mate,

Since asking this question i found the Legacy automation "Comment updates reply status" and adjusted that so it works again.

Is there any benefit to using an Automation over the Legacy automation to achieve this?

No worries, glad you managed to sort it! 👍

I would say that the "Automation" gives you a bit more freedom to customise your "if"/"and"/"or" in granular detail and I tend to prefer this way now, I used to use the now Legacy as my 'go to'. In your case here, to achieve this particular outcome in this scenario - either/or is fine in my opinion, and both would work. 

Automation has superseded Legacy in new JSM sites, so its the new custom automation model but if you're already using Legacy that's fine and will continue to work either way.

Hope that helps.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events