Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

How to create tasks from field inputs on a request in JWM?

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?

  • Security Badge
  • AD Access
  • MS Licences

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.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 23, 2023

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.

In theory, it should be once. Ideally, the users fill in a form then that creates an issue in the JWM that then cascades to various service projects.

I was playing with both fields in the form as well as the JWM issue. If we can do it in the forms, that'd be much better.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 24, 2023

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?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events