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,459,329
Community Members
 
Community Events
176
Community Groups

Approvers field doesn't get populated using Portal View

Edited

The Problem I have is that when a Portal Users selects the "submit" option on a Service Request ticket, the Approvers field is not populated.  

I have already reviewed a very similar issue reported here: https://community.atlassian.com/t5/Adaptavist-questions/How-to-set-up-approvers-in-Jira-Service-Desk/qaq-p/1110266
however, that is slightly different.

Screen Shot 2020-02-17 at 1.20.28 PM.pngScreen Shot 2020-02-17 at 1.21.28 PM.png


Everything works if the ticket is created using the Agent view, however, the approvers field does not get filled in when the ticket is submitted for approval from the Portal View.  The scrptrunner script reports script was successful and I can even see in the output of the log of the script that it retrieved the correct values from the User group. 

I just constantly get the error that "No Approvers selected" if Submit is from Portal View.  The ticket can be created in the Portal View and then an agent can Submit, and the field is populated correctly.  This is not feasible, nor efficient for how the process is set up for us currently.

Any suggestions?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events