Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Rows where User Story = LIBAPP-127 are in scope for this story
This block of fields is a repeatable field group and the component is being created as part of LIBAPP-88
Please see attached mock-ups and gifs from UX for how this should look/behave
Create, view and edit mode of the user record all need to be updated
Field labels should be as shown in "Field Label" column (please pay attention to the case)
Form edit controls (and values, where applicable) are specified in the "Input Type" column
Default values and functions are specified in the "Default Value/Function" column
Required fields are indicated in the "Required" column. Please note, some of these have input controls that will ensure they are populated (when records are created via the UI). Others will require a validation message if left blank but that is out of scope for this story (see https://folio-org.atlassian.net/browse/LIBAPP-114#icft=LIBAPP-114 for the validation story)
All other columns in the User Metadata spreadsheet can be ignored
I have one observation though, and that is naming of the button, which add a new address to a given user. This is named different than what is spec'ed in Filip's prototype. See image: adding-fieldgroup_0001_mouse.
Purpose: To enable the capture of 1 or more addresses for each User in FOLIO
Acceptance Criteria:
User Metadata Docment
Rows where User Story = LIBAPP-127 are in scope for this story
This block of fields is a repeatable field group and the component is being created as part of LIBAPP-88
Please see attached mock-ups and gifs from UX for how this should look/behave
Create, view and edit mode of the user record all need to be updated
Field labels should be as shown in "Field Label" column (please pay attention to the case)
Form edit controls (and values, where applicable) are specified in the "Input Type" column
Default values and functions are specified in the "Default Value/Function" column
Required fields are indicated in the "Required" column. Please note, some of these have input controls that will ensure they are populated (when records are created via the UI). Others will require a validation message if left blank but that is out of scope for this story (see https://folio-org.atlassian.net/browse/LIBAPP-114#icft=LIBAPP-114 for the validation story)
All other columns in the User Metadata spreadsheet can be ignored