Batch Importer (Bib/Acq) (UXPROD-47)

[UIDATIMP-179] UX update from Khalilah - Create/Edit Detail Record | Change Create <<record> or Update <<record>> button labels to [Save] Created: 17/Apr/19  Updated: 10/Jun/19  Resolved: 20/Apr/19

Status: Closed
Project: ui-data-import
Components: None
Affects versions: None
Fix versions: None
Parent: Batch Importer (Bib/Acq)

Type: Story Priority: P3
Reporter: Khalilah Gambrell Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: epam-concorde, epam-folijet, ux-consistency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones FOLIO-1788 Clone User Story: Create/Edit Detail ... Closed
Defines
defines UXPROD-1657 Data Import (Batch Importer for Bib A... Closed
Sprint: EPAM BatchLoader Sprint 14
Story Points: 1
Development Team: Folijet
Epic Link: Batch Importer (Bib/Acq)

 Description   

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

  1. 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
  2. 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]
  3. 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
  4. 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


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 18/Apr/19 ]

Viktor Soroka Here's that UI update story I mentioned. I'll fix the stories for match profiles so that they say Save instead of Create/Update - so I think we only need to fix the File Extension and Job Profiles. Thank you!

Comment by Viktor Soroka [ 18/Apr/19 ]

Ann-Marie Breaux, thank you. I will pick up the story in the current sprint since there is enough time to do that.

Comment by Viktor Soroka [ 19/Apr/19 ]

Hi Ann-Marie Breaux, I made the needed changes in the story as a part of UIDATIMP-137 Closed . Please check it on the testing-snapshot environment. Thank you.

Comment by Ann-Marie Breaux (Inactive) [ 19/Apr/19 ]

HI Viktor Soroka Scenario 3 is still using the old wording, at least in folio-snapshot. I'll check again in a day or two. Could you also make sure it was updated. Thank you!

Comment by Viktor Soroka [ 19/Apr/19 ]

Hi Ann-Marie Breaux, thank you for pointing that out. Updates are already merged, so please check on Monday on folio-snapshot as folio-testing seems is not trustworthy at the moment.

Comment by Ann-Marie Breaux (Inactive) [ 20/Apr/19 ]

Viktor Soroka Yep - all better now in folio-snapshot. Closing this ticket.

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