Issue Summary

This is reproducible on Data Center: (no)

Steps to Reproduce

1. In a Team Managed Project, Configure a form with a Start Date Custom Field and link the form to the Issue/request type as needed
2. Create an issue from the portal choosing the above Issue/Request Type and fill in the Start Date on the form
3. The issue will be created with the Start Date field on the request form section. Note that the Start Date is only on the form but not on the issue screen
4. Add this issue on a confluence calendar and try to drag and move the issue from one date to another on the calendar
5. Step 4 will fail with the Error : Failed to update the event, below message is seen on the splunk logs. Here customfield_12335 corresponds to the Custom Field : Start Date

   errors={customfield_12335=Field 'customfield_12335' cannot be set. It is not on the appropriate screen, or unknown.},reasons=[],status=400

      6. Reason : The Start Date update fails because the field is not available on the screen in a Team Managed Project

Expected Results

When the issue event is moved on the calendar the Start Date and End Date should be updated successfully and reflected in the issue as well.

Actual Results

The below exception is thrown in the splunk logs

message: [Limited to 100 per PT1M] REST response: 400: <400 BAD_REQUEST Bad Request,ErrorCollection[errorMessages=[],errors={customfield_12335=Field 'customfield_12335' cannot be set. It is not on the appropriate screen, or unknown.},reasons=[],status=400],[Cache-Control:"no-store, no-cache"]> 

Workaround

The Below workaround was accepted by the customer of this issue: PCS-355288 but might not be applicable to all

Here are the steps

1. Create a new custom field exactly same as the current start date custom field. Label the new custom field as "Display Start Date" (for example)
2. This new custom field Display Start Date will replace the original Start Date Field on the request form
3. Add the new "Display Start Date" field on the form and link it to itself
4. Remove the old "Display Start Date" field from the form and add it under the context fields section of the request type. Rename this field to, for example : "Updated Start Date" or anything else as needed.
5. Create an automation rule under the scope of the current project, that will copy the value from the new "Display Start Date" on the form to the original "Start Date" field on the screen upon creation of the issue.
6. The above steps will make sure that the "Display Start Date" field is available on the form and the "Updated Start Date" field is available on the screen.
7. This will make sure the drag and move feature on the calendar will successfully update the Start Date of the issue. 

Note: The drawback of this workaround is having two Start Dates fields(one on the screen, one on the form) but this should resolve the issue on the calendar. You can however rename the date fields as needed.