Affects Version/s: None
Fix Version/s: 5.4.19
Sprint:Sprint 33 - Ends Sept 18, Sprint 34 - Ends Sept 25, Sprint 35 - Ends Oct 10
When the user attempts to edit an existing script job in SR for Bamboo, they are unable to search for users within the field. This functionality works fine when adding a user.
- Navigate to "Add Ons" using the cog menu at the top right of the screen as an admin user.
- Select "Script Jobs" from the menu bar on the left.
- Click the cog menu under "Actions" and select "Edit" for an existing Script Job from the list of configured jobs (note: if none exist then you should create one.
- On the form that is presented, remove the existing user from the user field and begin to type the id / name of another user.
At this point you should notice that the search is not working.
I have already performed some preliminary investigation into this issue. We are using the same type of control as the confluence team with one exception. We have added the CSS class "user-picker" to the control. This gives control of creating the component to Bamboo. We are attempting to use a standard Bamboo component.
I have been working under the assumption that this could be happening because in the soy template, we only load the initialKey into the component, and perhaps it needs the entire user object.
The bottom line is, I have been unable to find any documentation from Atlassian regarding this control. This has made pinpointing and fixing the issue incredibly difficult.