Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Data import settings page's 3rd pane for Job Profiles: Header Caret Export Action - DRAFT

CSP Rejection Details

None

CSP Request Details

None

CSP Approved

None

Description

Purpose: To define the actions of the Header caret in the Data Import Settings Job Profiles header pane, except for the + New button (separate story for it).

As a staff person
I want to be able to take actions on one or more Job Profile settings in my file extension results list
So that I can easily work with these settings from the results list, rater than the individual job profile detail screen.

A-M asked Viktor if we have a central component for exporting delimited file that can be reused, or if we'll need to build it custom to DI

Live prototype:
https://xd.adobe.com/view/0bb2d8ab-aabd-4ff6-4d5a-faa59a93368e-7d83/

Brief video walk-through
https://www.dropbox.com/s/3slcv4v49qm92rv/2018-11-06-data-import-19.mp4?dl=0 (see 0:55-3:50 in the video)

Scenarios

  1. Scenario 1

    • Given the Job Profile third pane in the Data Import Settings (as shown in attachment 04-Settings File extensions.png)

    • When a User clicks the down caret next to the File extensions header

    • Then they should see a button that says "Reset all extension mappings to system defaults" (as shown in attachment 11-Settings file extensions options.png

  2. Scenario 2

    • Given the Reset all extension mappings... button

    • When a user clicks that button

    • Then FOLIO should display the modal as shown in attachment 12-Settings file extensions reset modal.png

  3. Scenario 3

    • Given the Reset all extension modal

    • When the User clicks Cancel

    • Then the modal should close without deleting any user-defined extensions or resetting any system-supplied extensions.

  4. Scenario 4

    • Given the Reset all extension modal

    • When the User clicks Reset all

    • Then the modal should close

    • And any user-input file extensions should be deleted

    • And any system-supplied default file extensions should be reset to their default settings (recreated if deleted by a user, set back to their original settings if edited by a user)

    • And the file extensions 3rd pane should basically look like it did the first time it was displayed in the tenant, before any edits were made by any users

NOTE: blocked until backend work is done to create data schema and APIs

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Viktor SorokaApril 16, 2019 at 9:17 AM

, I think so, please specify fields which need to be exported in the description. Thank you.

Ann-Marie BreauxApril 16, 2019 at 9:12 AM

Good - so it sounds like I can clean up the description and open this story. Is that right?

Viktor SorokaApril 16, 2019 at 8:54 AM

Hi , there is indeed existing component for that purpose. We may reuse it unless it works for our scenario.

Ann-Marie BreauxApril 16, 2019 at 7:46 AM

Hi Have you had a chance to review the export options? Is there a central component that we can use, or can we borrow from one of the other apps/Jira issues noted in the comment above this one, or would we need to build it from scratch for Data Import? Thank you!

Ann-Marie BreauxApril 2, 2019 at 8:05 PM

Hi Here are some examples of CSV export stories in Jira:

For requests: , , , , ,

For user loans: , , ,

General: ,

I've also attached a requests CSV export as an example. What do you think? Is this a central component we can work with, or would we be building it from scratch? If we have to start from scratch, then I think I might deprioritize the profile export for now.

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Development Team

Folijet

Parent

Release

Not Scheduled

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 20, 2019 at 7:10 AM
Updated August 10, 2023 at 6:35 AM
Loading...