gitea_admin/asset-management
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: leave Assigned by out of the Assign form

Browse Source 
field_5 is a select in the builder and the runtime rejects any value not
in its options, so sending employee names failed with "Assigned by must be
one of the listed options". Drop it from the form, as Reassign already does
for field_11, until the builder field is changed to text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
vamsi.balaga 2026-10-27 18:37:07 +05:30
parent 1004ad4895
commit 96718d173c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/api/assets.js
View File

@ -229,9 +229,10 @@ export const ASSET_ASSIGN_ACTIVITY_ID = 'd18815a4-4e74-480d-a943-67dce894412f'
/** Fields the user fills in. */ /** Fields the user fills in. */
export const ASSET_ASSIGN_FIELDS = [ export const ASSET_ASSIGN_FIELDS = [
{ id: 'field_1', label: 'Assigned date', type: 'date' }, { id: 'field_1', label: 'Assigned date', type: 'date' },
// The builder has no options for Assigned by, so the form offers the active // Assigned by (field_5) is left out of the form on purpose: it is a select in
// employees' names (`employeeOptions`, filled in by the dialog). // the builder and the runtime rejects any value not in its options ("Assigned
{ id: 'field_5', label: 'Assigned by', type: 'select', options: [], employeeOptions: true }, // by must be one of the listed options"), so employee names can't go there.
// Add it back, with `employeeOptions: true`, once the builder field is text.
{ id: 'field_6', label: 'Remarks', type: 'longtext' }, { id: 'field_6', label: 'Remarks', type: 'longtext' },
{ {
id: 'field_21', id: 'field_21',