Done
Details
Assignee
Ann-Marie BreauxAnn-Marie Breaux(Deactivated)Reporter
Khalilah GambrellKhalilah GambrellPriority
P3Story Points
1Sprint
NoneDevelopment Team
FolijetTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Ann-Marie Breaux
Ann-Marie Breaux(Deactivated)Reporter
Khalilah Gambrell
Khalilah GambrellPriority
Story Points
1
Sprint
None
Development Team
Folijet
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 17, 2019 at 11:35 AM
Updated June 10, 2019 at 8:35 AM
Resolved April 20, 2019 at 6:02 AM
UI Update from Khalilah
Currently apps have a variety of button labels for saving a record and some labels are unclear.
We have a new UI requirement to standardize the button label for saving a detail record.
New button label will be Save
Scenarios
Scenario 1
Given the Settings/Data Import/File extensions
When a user creates a new file extension and wants to save it
Then the button label should read Save instead of Create file extension
Scenario 2 [already done]
Given the Settings/Data Import/File extensions
When a user updates an existing file extension and want to save it
Then the button label should read Save [no change needed, button already says Save]
Scenario 3
Given the Settings/Data Import/Job profiles
When a user creates a new job profile and wants to save it
Then the button label should read Save instead of Create job profile
Scenario 4
Given the Settings/Data Import/Job profiles
When a user updates an existing job profile and wants to save it
Then the button label should read Save instead of Update job profile or Save job profile