Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 90
-
5
-
Spitfire
Description
Background: Currently an option does not have a unique identifier. As a result,
- if the option is renamed there is no way to reference this change and ensure this change is made across all records that currently store the option.
- there is no unique identifier that can be used to support when to display a Delete confirmation modal
- setting a default option(s) is difficult to manage
- supporting drag and drop of options is difficult to implement
Requirement: Each option requires an unique identifier AND change should be applied to the following custom fields that support options
- Single Select
- Multi-Select
- Radio button
Development work
- Need to store
- Need to ensure uniqueness
- Need to support auto-generation
- Need to support option/value assignment codes
TestRail: Results
Attachments
Issue Links
- defines
-
MODUIMP-21
Support custom field options ids
-
- Closed
-
-
UXPROD-2288 Q2 2020 | Custom Fields (for User Record and as General Platform Feature) Development
-
- Closed
-
- is required by
-
STSMACOM-330
Input types: Single Select, Multi-Select, Radio button: Each option should have a code field
-
- Closed
-
-
STSMACOM-339
Support unique id for custom fields options
-
- Closed
-
- requires
-
MODUSERS-195 Upgrade to RAML Module Builder 30.0.0
-
- Closed
-