-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
4.1.0
-
1
-
Severity 3 - Minor
-
2
-
Issue Summary
When viewing an issue through the SD Queue and adding a custom field with the type 'Text field' through Admin > Add Field button results in the screen loading indefinitely and the 'Edit Field' button grayed out.
For example, if you view the issue via the Queue and the URL of the issue is 'http://localhost:8081/projects/SERV/queues/custom/1/TEST-19', the add field will not work accordingly. However, this will feature will work accordingly if you view the issue directly via the URL 'http://localhost:8081/browse/TEST-19'.
Did some testing in 4.1.3, it seems to be affecting all custom fields, but only the Issue Type 'Service Request'. In 4.1.0, it is reproducible only with the custom field with the type 'Text field(single line)' with all Issue Types.
Steps to Reproduce
- Create a custom field with the type 'Text field(Single Line)'.
- Ensure that the field is associated with a screen in the Service Desk project.
- Go to your Service Desk 'Queue', view the issue details from there.
- Click on Admin > Add field
- Type the name of a custom field.
- The correct field is suggested and selected.
- Click on the blue 'Edit field' button to edit the field value for the current issue
- Clicking on 'Cancel' does not do anything either.
Expected Results
The field is successfully added to the View Issue Screen of the issue.
Actual Results
The process hangs and the 'Edit Field' button grays out. 
You will see this error being thrown in the Browser Console.
Uncaught Error: Handler not found for 'issueEditor:fields'
at d.getHandler (batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&richediton=true&user-logged-in=true:1875)
at d.request (batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&richediton=true&user-logged-in=true:1878)
at constructor.request (batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&healthcheck-resources=true&jag=true&jaguser=true&jira.create.linked.issue=true&locale=en-UK&richediton=true&user-logged-in=true:1911)
at getFieldsOnSelectedIssue (batch.js?locale=en-UK:2949)
at Function._isFieldVisible (batch.js?locale=en-UK:427)
at Object._analytics (batch.js?locale=en-UK:427)
at c (batch.js?locale=en-UK:65)
at Object.fireWith [as resolveWith] (batch.js?locale=en-UK:65)
at Object.a.<computed> [as resolve] (batch.js?locale=en-UK:65)
at a._onCompleteSuccess (batch.js?locale=en-UK:394)
Workaround
Access the issue directly instead of viewing it through queue.
- links to
[JSDSERVER-6659] When viewing an issue through the SD Queue, then, adding a custom field with the type 'Text field' through Admin > Add Field button results in the screen loading indefinitely and the 'Edit Field' button grayed out.
I was not able to reproduce this using the steps provided in neither JSD 4.1.3 nor 4.1.0. I had a suspicion that the JSW might have an impact on this (since the JS log points out the JSW context for the bundle.js file), but I was unable to reproduce the issue in neither of the versions after installing JSW 8.1.3 and 8.1.0 (correspondingly).
Closing this for now.
Cheers,
Jira Service Desk team
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center