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

[UXPROD-2743] NFR: Reuse components from the data-transfer-components repository Created: 01/Jul/20  Updated: 18/Nov/20  Resolved: 17/Nov/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Mariia Aloshyna Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: data-import, epam-folijet, tech-debt, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by UIDATIMP-557 SPIKE: Investigate possibility to re-... Closed
is defined by UIDATIMP-571 Reuse <EndOfItem> component from data... Closed
is defined by UIDATIMP-572 Reuse <JobLogs> component from data-t... Closed
is defined by UIDATIMP-573 Reuse <JobsList> component from data-... Closed
is defined by UIDATIMP-574 Reuse <JobsListAccordion> component f... Closed
is defined by UIDATIMP-575 Reuse <Progress> component from data-... Closed
is defined by UIDATIMP-576 Reuse utils from data-transfer-compon... Closed
is defined by UIDATIMP-578 Reuse <FullScreenForm> component from... Closed
is defined by UIDATIMP-579 Reuse <FileUploader> component from d... Closed
is defined by UIDATIMP-580 Reuse <Preloader> component from data... Closed
is defined by UIDATIMP-581 Reuse <SearchResult> component from d... Closed
is defined by UIDATIMP-582 Reuse <SearchForm> component from dat... Closed
is defined by UIPFIMP-24 Reuse utils from data-transfer-compon... Closed
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Large < 10 days
Back End Estimate: Out of scope
Back End Estimator: Ann-Marie Breaux (Inactive)
Development Team: Folijet

 Description   

This feature is created to collect all tasks related to reusing components from the `data-transfer-components` repository in the `data-import` module.

We would like to reuse components common to the data-import and data-export modules. The data-transfer-components repository was created to avoid code duplication (because data-export and data-import use a lot of similar components) and currently it contains common components. So the main goal is to import shared components from this repository to data-import and get rid of duplicates. What's more, all components in data-transfer-components repository are covered by tests already, so it will help us to maintain a high level of code stability.

End of Q3 2020: 5 of 12 closed



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 01/Jul/20 ]

Hi Mariia Aloshyna and Ivan Kryzhanovskyi I'm sorry - I've gotten lost on this one. Is this to help with getting the UI automated testing restarted, or something else?

Comment by Mariia Aloshyna [ 01/Jul/20 ]

Hi Ann-Marie Breaux This one is about reusing components common to the data-import and data-export modules. the data-transfer-components repository was created to avoid code duplication (because data-export and data-import use a lot of similar components) and currently it contains common components. So the main goal is to import shared components from this repository to data-import and get rid of duplicates. What's more, all components in data-transfer-components repository are covered by tests already, so it will help us to maintain a high level of code stability.

Comment by Ann-Marie Breaux (Inactive) [ 01/Jul/20 ]

Thanks, Mariia Aloshyna I understand now. I'm going to add some of your comment to the description, so that I don't ask again!

Comment by Mariia Aloshyna [ 01/Jul/20 ]

Thank you Ann-Marie Breaux!

Comment by Ann-Marie Breaux (Inactive) [ 06/Jul/20 ]

Hi Mariia Aloshyna I saw you've created stories for this - do you have a sense - are each of them point size 1 or 2 ish or 5 ish? Would it maybe make sense to perhaps take 1 per sprint? That way we work them down, but don't sacrifice too much of the sprint to tech debt.

cc: Ivan Kryzhanovskyi

Comment by Mariia Aloshyna [ 06/Jul/20 ]

Hi Ann-Marie Breaux Most of these tasks are really small - about 1-3 sp. I think it makes sense to take one or a few tasks per sprint, especially since they are not critical.

Comment by Ann-Marie Breaux (Inactive) [ 06/Jul/20 ]

Hi Mariia Aloshyna That sounds good - 1 or max 2 per sprint, and we drop them back to the backlog if other more important bugs or new functionality comes up. Similar to how we're doing accessibility fixes right now.

Comment by Viktor Soroka [ 17/Nov/20 ]

Ann-Marie Breaux, thank you for this epic. Folijet UI folks performed nicely on this one. Great cooperation between Folijet and Concorde teams.

cc Magda Zacharska

Comment by Ann-Marie Breaux (Inactive) [ 18/Nov/20 ]

Glad to hear it, Viktor Soroka!

cc: Ivan Kryzhanovskyi Oleksii Kuzminov

Generated at Fri Feb 09 00:26:29 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.