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
I am trying to automate creation of tasks that come off a request. The concept is basically that the JWM project would act as a conduit for tasks that then need to disseminate to a few other teams.
So idea is you would have a field like:
What do you require?
The idea is that each one of those options would create a new task in the relevant service project that handles those sort of requests. It's basically a simple request that sits across a set of teams in order to accomplish. This automation would make it a lot easier to see how we're progressing across the company to achieve these.
Any ideas? So far I've been toying with 'When a field changes' but it doesn't seem to let you set it to trigger when a certain value is picked.
Hello @Alex Lock
In the example you provided, is the "What do you require?" field being set when the issue is created? Is it ever changed after that?
Is that an example of a JWM form, or an actual field in the resulting JWM issue?
Can the field in the JWM issue end up with more than one value?
If it is set when the issue is created then your Automation Rule should use the "Issue Created" trigger.
After that the next steps depend on whether or not the field that holds the information is a multiple selection field or a single selection field.
Hello @Alex Lock
I don't work a lot with JWM Forms, but it appears that the fields on the forms correspond to fields in the issue.
Is the field a multiple selection fields or a single selection field?