We currently have a Dynamic Field bug experienced by only one user.
Field Configuration:
We have a Compliance Requirement dynamic field. Within the configuration for this field, the Desired Date (date picker) field is related to the option Yes, and is set to be required. (If Compliance Requirement is set to No, the Desired Date field does not display on the screen.)
Screen Shot 2016-02-12 at 11.18.41 AM.png
Problem:
When the one particular user experiencing this problem creates issues in this project, setting the Compliance Requirement field to Yes does not in turn display the Desired Date field. Because the Desired Date field is required, he is then unable to actually submit his issue.
Workaround:
To work around this, this user can set the Compliance Requirement field to No when creating the issue, then go back and edit the issue after it has been created to set the Compliance Requirement field to Yes and select a Desired Date.
Troubleshooting:
We have isolated this issue to this user's profile. When he logs in to another computer or browser, the same behavior occurs. If other users with identical permissions log in to his browser, the Desired Date field comes up fine.
Community moderators have prevented the ability to post new answers.
Hi Lana,
This is really strange behavior. Are there any errors in atlassian-jira.log or in java-script console? You can create ticket in InTENSO customer portal: https://intenso.atlassian.net/servicedesk/customer/portal/5
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.