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

Set default assignee to unassigned

We're looking at using Jira Service Management but the main issue we're running into is that it requires an assignee to be specified.

Essentially in all of the request forms if we set the default assignee to unassigned we get an error "Enter a valid preset value" Changing this to a specific user means the form works and the tickets get created but obviously, that means that user will get all new tickets assigned to them and it would be more difficult for everyone to track which ones they're working on and which tickets need picking up. 2023-10-26_11-19-24.png

From looking at similar queries I've found we might be able to do it by changing the default assignee in the project settings but we're running into another problem. All of the site admins and the org admins are unable to change this setting even when they're set as admins in the service desk as well as on Jira as a whole so we're really not sure who is able to.

2023-10-26_11-19-43.png

 

I've tried using the automation settings to get around it but it's running into a similar issue.

2023-10-26_11-29-09.png

The obvious solution to me is to create another user "ToBeAssigned" or something along those lines that we essentially set as the default assignee but that means potentially paying for another license which we'd like to avoid if we can.

 

Thanks.

1 answer

1 accepted

2 votes
Answer accepted

Sorted it. This setting was the culprit. Was set to off, setting it to on allows both settings to be set to unassigned.

 

2023-10-26_11-38-29.png

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