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: 

How can I make an effective custom date default to only 1/01/1900?

Deleted user
September 17, 2020

I created a custom date field called Effective Date. But the user wants the date to immediately default to 1/01/1900. How can I make it default to 1/01/1900 on the Portal Screen and nobody can be able to edit this Effective Field.

The instruction is to run the preview the portal screen and immediately let the effective date "...Default to 1/01/1900 and do not allow edits to be made to this custom Effective Date field".

 

Thanks again,

alaso

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Martin Bayer _MoroSystems_ s_r_o__
Community Champion
September 17, 2020

hi @[deleted] I'm sorry but I'm not aware of possibility of displaying read only field when creating request via portal.

You can set default value using custom field setup:

Selection_541.pngBut the only option to set the field as read only is to user Behaviours  function in ScriptRunner (https://scriptrunner.adaptavist.com/5.6.8/jira/behaviours-overview.html).

You can HIDE field on portal so noone can edit it when creating request, but it is probably not what you need.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events