[UICFIELDS-23] Spike: Define Custom Field UI design implementation approach Created: 04/Sep/19  Updated: 24/Feb/20  Resolved: 02/Oct/19

Status: Closed
Project: ui-customfields
Components: None
Affects versions: None
Fix versions: 1.0.0

Type: Story Priority: P3
Reporter: Khalilah Gambrell Assignee: Yurii Danylenko
Resolution: Done Votes: 0
Labels: epam-spitfire, front-end
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to STSMACOM-253 Create a page for Custom Fields previ... Closed
relates to STSMACOM-254 Create and edit Custom Fields list AN... Closed
relates to STSMACOM-266 Create and edit page for Custom Field... Closed
relates to STSMACOM-267 Settings | Custom fields | Edit: Drag... Closed
relates to STSMACOM-301 Create an Input Type = Text area Closed
relates to STSMACOM-302 Input - Create a page for Custom Fiel... Closed
relates to STSMACOM-314 Create an Input Type = Single Checkbox Closed
relates to UXPROD-33 Custom Fields (for User Record and as... Closed
relates to UXPROD-2143 Q1 2020/Q2 2020 | Custom Fields (for ... Closed
Sprint: eHoldings Sprint 73, eHoldings Sprint 72
Story Points: 2
Development Team: Spitfire

 Description   

Objective: Define Custom Field UI design implementation approach

Outcome: Create requirements to support UI design

Timebox: 8 hours.

Requirements:

  • Implement custom fields preview page in Settings(Stripes smart components)
  • Settings edit page with a set of editable custom field boxes(Stripes smart components)
  • React dnd accessible library https://github.com/atlassian/react-beautiful-dnd

Generated at Thu Feb 08 22:33:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.