-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5
-
Severity 3 - Minor
-
0
-
Issue Summary
When configuring a User Property custom field, users need to provide the following combination for the default value:
<fieldname>:<user property name>
The above allows to populate the field with the Jira User Property value configured for that specific property key based on the user set in the defined user field.
If the default value is misconfigured and the User Property custom field's name is provided, this causes an internal loop resulting in an error. During a transition when the custom field is called, the error when trying to set the value for the User Property field causes the transition to fail.
In order to prevent this, the system should prevent the User Property field itself being set through a validation check.
Steps to Reproduce
- Create a User Property Field (<255 characters) custom field called Test User Property
- Configure the default value of this field to the following - we are using Phone as the Jira Issue Property:
Test User Property:Phone
- In the testing completed the context was configured to a particular project, leaving the broken field global may break projects it's associated with
- Add the field to the field configuration scheme and associate with a screen
- Try to transition an issue in the impacted project
Expected Results
The custom field default value returns an error indicating the field name provided matches that of the User Property field itself and this value cannot be used.
Actual Results
There are no validation checks completed on the field name and if the default value is saved, transitions break on project(s) associated with the context and field configuration schema.
Error observed via the network tab:
Request URL: https://your-site.atlassian.net/rest/api/2/issue/EXAMPLE-123/transitions Request Method: POST Status Code: 500
Workaround
Remove or change the default value configuration to use another field.
- mentioned in
-
Page Failed to load
The User Property custom field does not validate the default value to prevent the User Property field itself being set which causes transitions to fail
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5
-
Severity 3 - Minor
-
0
-
Issue Summary
When configuring a User Property custom field, users need to provide the following combination for the default value:
<fieldname>:<user property name>
The above allows to populate the field with the Jira User Property value configured for that specific property key based on the user set in the defined user field.
If the default value is misconfigured and the User Property custom field's name is provided, this causes an internal loop resulting in an error. During a transition when the custom field is called, the error when trying to set the value for the User Property field causes the transition to fail.
In order to prevent this, the system should prevent the User Property field itself being set through a validation check.
Steps to Reproduce
- Create a User Property Field (<255 characters) custom field called Test User Property
- Configure the default value of this field to the following - we are using Phone as the Jira Issue Property:
Test User Property:Phone
- In the testing completed the context was configured to a particular project, leaving the broken field global may break projects it's associated with
- Add the field to the field configuration scheme and associate with a screen
- Try to transition an issue in the impacted project
Expected Results
The custom field default value returns an error indicating the field name provided matches that of the User Property field itself and this value cannot be used.
Actual Results
There are no validation checks completed on the field name and if the default value is saved, transitions break on project(s) associated with the context and field configuration schema.
Error observed via the network tab:
Request URL: https://your-site.atlassian.net/rest/api/2/issue/EXAMPLE-123/transitions Request Method: POST Status Code: 500
Workaround
Remove or change the default value configuration to use another field.
- mentioned in
-
Page Loading...