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,558,800
Community Members
 
Community Events
184
Community Groups

Approvals in Simplified Workflow

Edited

Our business teams often have peer review workflows where one member of the team submits work, and we would like to record that a different member of the team approved the work.

This can be done in JSM or through company managed workflow conditions, but I was wondering how this can be accomplished through JWM in the simplified workflow.

 

Note that the pool of submitters and approvers are the same, so we can't just use permissions to restrict.

2 answers

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 27, 2023

Hi Michael,

There is nothing built into JWM like there is for JSM. So you would have to do a lot of manual adding in of things. For instance, you would need to create a custom field for someone to grant the approval - something as simple at Approved? Yes/No

Then you can build some automation rules to do things like auto-transition the issue, re-assign it, etc. based on the value of the field changing. 

If you don't want others to change the value then you can incorporate Issue Level Security or handle with putting the custom Approved? field in a transition screen and restricting access to the transition using a Condition on the transition.

Note that the pool of submitters and approvers are the same, so we can't just use permissions to restrict.

Suggest an answer

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

Atlassian Community Events