[STSMACOM-285] Custom Field: Input Type: Single select dropdown Created: 07/Aug/19 Updated: 26/May/20 Resolved: 04/May/20 |
|
| Status: | Closed |
| Project: | stripes-smart-components |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 4.0.0 |
| Type: | Story | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Владислав Велицкий |
| Resolution: | Done | Votes: | 0 |
| Labels: | epam-spitfire, front-end | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | eHoldings Sprint 87 | ||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||||||
| Description |
|
As a librarian ScreenshotSettings > Users > Custom fields View page handling single select dropdown
Create/Edit Single select dropdown Settings Requirement
Acceptance CriteriaGiven I am on the Edit Custom field page Given I am on the Edit Custom field page Given I have entered [Major] for the single select dropdown Given I have entered more than 65 characters in the field label Acceptance Criteria - Single select dropdown options requirements - option labelGiven I am on the Edit Custom field page Given I have accessed the custom field Major Given I have entered more than 65 characters in the single select option label Given I have entered [History] for the option label Given I have entered [History] for the option label Given I have entered several options Given I have entered several options |
| Comments |
| Comment by maksym_dryha [ 16/Mar/20 ] |
|
Khalilah Gambrell, Filip Jakobsen, the flow described in the story contradicts what I see on Filip's mockups. The design implies that we chose the type of dropdown (MULTI_SELECT_DROPDOWN or SINGLE_SELECT_DROPDOWN) using the list that is shown after a user clicks the "Add custom field" button, whereas the story requirement is that in the list of custom field types we should only see "Dropdown" option, which then can be configured to be multi-select or single-select. |
| Comment by Khalilah Gambrell [ 16/Mar/20 ] |
|
maksym_dryha, I haven't updated the story yet |
| Comment by Denys Bohdan [ 26/Mar/20 ] |
|
Khalilah Gambrell have you had a chance to update the story with regards to Maksym's question? |
| Comment by Khalilah Gambrell [ 26/Mar/20 ] |
|
Denys Bohdan - not yet. |
| Comment by Khalilah Gambrell [ 30/Mar/20 ] |
|
Denys Bohdan and maksym_dryha, I have updated the requirements. |
| Comment by Khalilah Gambrell [ 15/Apr/20 ] |
|
Removed Code requirement. Needs backend work. |
| Comment by Khalilah Gambrell [ 17/Apr/20 ] |
|
Will need to address in another story how to reset the default value. |
| Comment by Khalilah Gambrell [ 27/Apr/20 ] |
|
maksym_dryha, Владислав Велицкий, and Denys Bohdan, please review the requirements updates. |
| Comment by Khalilah Gambrell [ 28/Apr/20 ] |
|
Владислав Велицкий, based on requirement updates, any additional updates to the requirements? |
| Comment by Владислав Велицкий [ 28/Apr/20 ] |
|
Khalilah Gambrell, no, thanks, these requirements are enough. 'Default' functionality will be implemented in STSMACOM-292. |