Uploaded image for project: 'ui-data-import'
  1. ui-data-import

Create data import settings page's 3rd pane for Jobs Profiles



    • EPAM BatchLoader Sprint 13, EPAM BatchLoader Sprint 14
    • 5
    • Folijet


      Purpose: To be able to create and save job profiles (comprised of matches, actions, and data mappings), so that they can be applied to current and future files that are being imported.

      As a staff person
      I want to be able to create and store job profiles for the Data Import app
      So that I can assemble matching, action, and mapping profiles in various configurations
      And so that I do not have to reconstruct these configurations every time I import a new file


      • This story is only for creating the outline of the job profile pane on the settings screen. There will be additional stories for creating the create/edit screens for jobs and for the detailed configuration of jobs.

      Live prototype:

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


      1. Scenario 1
        • Given the Data Import Settings
        • When a User clicks the Job profiles setting in the second pane
        • Then the Job profiles option in the second pane should turn grey with white text and
        • A third pane should open, displaying a list of the existing job profiles
        • As shown in attachment 20-Settings Job profiles.png
      2. Scenario 2
        • Given the Job profiles third pane
        • When displaying the pane
        • Then the format of the pane should be as follows, as shown in attachment 20-Settings Job profiles.png
          • Header: [job profile icon] followed by Job profiles followed by a down caret [No action for now - action is covered by future story] no caret but we'll deal with that in future story
          • Subheader: # profiles, where # is the number of job profiles in the results list
          • New button [no plus sign] on right side of header [No action for now - action is covered by future story]
          • Top of results list: search box [No action for now - action is covered by future story]
          • Results list column headers
            • Check box [Can check and uncheck the checkboxes, but no action for now; top checkbox does not yet affect the individual line checkboxes for now, and all action is covered by future story]
            • Name
            • Tags
            • Updated
            • Updated by
          • Results list data elements per row (alternating rows in white and grey)
            • Check box [No action for now - action is covered by future story]
            • Job profile icon followed by job profile name
            • Tags icon followed by tags; multiple tags are separated by comma [space], e,g. first, second, third
            • Edit pencil icon followed by most recent update date
            • User icon followed by most recent updater's name (firstname lastname) and username in parentheses, e.g. John Doe (johndoe)
          • Default sort order should be alphabetical A-Z by profile name see attached - alphabetical by name doesn't seem to be working quite right; per Viktor, it's a backend problem MODDICONV-34
          • User should be able to sort and reverse sort by clicking on any of the column headers
          • End of list component (icon and wording)
      3. Scenario 3
        • Include standard automated testing coverage; add screenshot or other details to confirm test coverage is in place


      TestRail: Results


          1. 20-Settings Job profiles.png
            20-Settings Job profiles.png
            242 kB
          2. Coverage.png
            71 kB
          3. Sort ascending problem.PNG
            Sort ascending problem.PNG
            234 kB
          4. Sort descending problem.PNG
            Sort descending problem.PNG
            233 kB

          Issue Links



                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Ann-Marie Breaux Ann-Marie Breaux
                0 Vote for this issue
                2 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases