-
Bug
-
Resolution: Fixed
-
Medium
-
2.2-OD-04, 2.4.3
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
If a custom field of the text variety is created, and a default value is assigned to that text field, it will populate in that field through the standard JIRA UI, but not in requests created through a Service Desk portal.
Steps to Reproduce
- Create a custom Text Field
- Add a default value to that field
- Add the field to a screen used by a Service Desk project
- Add that field to a Service Desk request type
- Bring up the create screen for that request
Expected Results
Default value will be displayed in the Customer Portal
Actual Results
The field is empty, without any default value
Notes
The issue seems similar to JSD-403
The fix should include for other custom field as well (date picker, number, etc.)
- has a derivative of
-
JSDSERVER-1926 Custom Field assumes default values even if the field is set as empty on customer portal
-
- Closed
-
-
TESLA-842 Failed to load
- is duplicated by
-
JSDSERVER-1967 Custom Field Type Number's Default Values Do Not Get Populated On SD Customer Portal
-
- Closed
-
- relates to
-
JSDCLOUD-1295 Custom text field default values do not get populated on create screens in the portal
-
- Closed
-
-
JSDSERVER-403 Customer Portal date custom field is not filled in with the default value.
-
- Closed
-
- mentioned in
-
Page Loading...
- was cloned as
-
DESK-4158 Loading...
[JSDSERVER-1295] Custom text field default values do not get populated on create screens in the portal
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304481 ] | New: JAC Bug Workflow v3 [ 3126464 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2058619 ] | New: JSD Bug Workflow v5 - TEMP [ 2304481 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056139 ] | New: JSD Bug Workflow v5 [ 2058619 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1955584 ] | New: JSD Bug Workflow v5 - TEMP [ 2056139 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1615905 ] | New: JSD Bug Workflow v5 [ 1955584 ] |
Description |
Original:
h4. Summary
If a custom field of the text variety is created, and a default value is assigned to that text field, it will populate in that field through the standard JIRA UI, but not in requests created through a Service Desk portal. h4. Steps to Reproduce # Create a custom Text Field # Add a default value to that field # Add the field to a screen used by a Service Desk project # Add that field to a Service Desk request type # Bring up the create screen for that request h4. Expected Results Default value will be displayed in the Customer Portal h4. Actual Results The field is empty, without any default value h4. Notes The issue seems similar to The fix should include for other custom field as well (date picker, number, etc.) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1295]. {panel} h4. Summary If a custom field of the text variety is created, and a default value is assigned to that text field, it will populate in that field through the standard JIRA UI, but not in requests created through a Service Desk portal. h4. Steps to Reproduce # Create a custom Text Field # Add a default value to that field # Add the field to a screen used by a Service Desk project # Add that field to a Service Desk request type # Bring up the create screen for that request h4. Expected Results Default value will be displayed in the Customer Portal h4. Actual Results The field is empty, without any default value h4. Notes The issue seems similar to The fix should include for other custom field as well (date picker, number, etc.) |
Link |
New:
This issue relates to |
Labels | Original: fug | New: affects-cloud affects-server fug |
Workflow | Original: JSD Bug Workflow v2 [ 1603107 ] | New: JSD Bug Workflow v4 [ 1615905 ] |
This issue is not fixed.