The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Is it possible to set Unassigned as a default value for a custom field of the type User Picker (single user)?

Is it possible to set Unassigned as a default value for a custom field of the type User Picker (single user)?

Vincent Mouwen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 12, 2015

To stories we want to assign, besides the assignee, a support assignee. We created a custom field of the type User Picker (single user) which we called Support Assignee. This all works fine but it's not possible to set as a default value "Unassigned". We need this because if there is no value in the field it is not shown on the issue.   

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Tulika Panda
October 14, 2020

Did anyone get a resolution for this? Our users are facing the same issue.

Kian Stack Mumo Systems
Community Champion
October 14, 2020

Hi Tulika,

Is this in Cloud or Server? What problem are you facing exactly?

Thanks!

Kian

0 votes
Deleted user
October 11, 2019

Is it possible to preset Unassigned or NONE on the custom field of type single user picker at the time of issue creation? This will enable fields to be visible after Saving the issue form.

0 votes
Kian Stack Mumo Systems
Community Champion
June 12, 2015

It's true that you can't select "unassigned" as an option. One possible route you could take is to create a dummy user that will be used to represent any that do not have a value in "Support Assignee". That would cause it to be populated, but not refer to a user it shouldn't. 

Davide Cutaia
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 5, 2018

Yes, I have the same problem.

I have created a field "Participants" as I need to keep other people informed on the status of a specific task.

But if I leave it optional (and blank) on the Create Screen, then it will not appear when the issue is created.

If I set as a required field this creates problems as i might not have any participants to add. 

Any idea on how to solve this?

Thomas Reggi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2019

I am also having this issue.

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question