Possible UI only projects
This document is for FE developers only at this time. More details will be posted to JIRA.
Work or JIRA | FE Dev lead (or Dev team) assigned | Notes | Status |
|---|---|---|---|
Clean your stripes console | All | Any developer can do this work regardless of FOLIO dev experience. Next steps
| |
Setup and Run large data load functional tests AND Performance (API) Tests | All | Need to provide more details Can Manual QA or PO write test cases? | |
Remove the 10 records limit EVERYWHERE. | All |
Next steps:
| |
RTL/JEST > Prokopovych tests backlog | Any | @Anton Emelianov (Deactivated) will work with teams to break up work across the following teams: Volaris, Spitfire, Thunderjet, Folijet * ui-inventory: https://folio-org.atlassian.net/browse/UXPROD-3322 | |
Setup and execute e2e automated tests for your own apps | Any | @Anton Emelianov (Deactivated) and @Oleksii Petrenko will work with teams. Ideally teams should execute automated tests for their apps. AQA can then focus on Prokopovych and Vega smoke tests automation. Next steps: Talk with Anton after Thursday 4/28 if interested. | |
Setup and execute e2e automated tests for Vega team | Any | Vega team needs assistance with smoke automated tests I believe. @Anton Emelianov (Deactivated) and @Oleksii Petrenko can you figure it out? Next steps: Talk with Anton after Thursday 4/28 if interested. | |
Create <<ui-module>>Dashboard widget (Dashboard Use Cases) | Not ready | Need requirements | |
Print a detail record | Needs PO analysis |
 | |
Print a detail record of MARC SRS | Needs PO analysis | Inventory supports print of MARC records as they are displayed in SRS. Implement Action menu: Print source, as the last Action menu item for Inventory actions. | |
Print a detail record of Instance, Holdings and Item | Needs PO analysis | Inventory supports print of instance, holdings and item records. Implement Action menu: Print Instance. At the second last Action menu item for Inventory actions. So after View requests, and before: Print source. | |
Thunderjet | We inadvertently broke detail-pane printing in STCOM-872 and need to restore it. Please fix in Morning Glory | ||
Focus management | Any | Define a technical approach for improving focus management. Context: Customers state that FOLIO is "too clicky". To do anything requires multiple mouse clicks. This technical approach will apply/improve focus management to help minimize some of the "too clicky" complaints. Examples that we need to do
| |
Refactor infotip component https://folio-org.atlassian.net/browse/STCOM-681 https://folio-org.atlassian.net/browse/STCOM-722 | Any | Infotip must be updated to address accessibility issues. | |
Refactor Timepicker component https://folio-org.atlassian.net/browse/STCOM-326 https://folio-org.atlassian.net/browse/STCOM-694 https://folio-org.atlassian.net/browse/STCOM-568 https://folio-org.atlassian.net/browse/STCOM-569 | Hold | https://folio-org.atlassian.net/browse/STCOM-326 - is this still needed? DB: I thought we were refactoring in favor of "stripes-final-form" | |
Any | Expose Ref to control in `<Selection>` and `<Select>` | ||
Any | MetaSection should correctly display unknown user values as "Unknown", not "System user" | ||
Create new Interactors | N/A | @John Coburn please provide the list of remaining interactors that need to be created. | |
Create/ update Stripes <specific topic> documentation | Any | Identify documentation
| |
Any | Correctly handle i18n in ControlledVocab. Note: this will be a breaking change and involve refactoring across every app that uses CV due to the need to pass in new translation strings. It's not so much "the code is wrong" as "the i18n is wrong". | ||
Any | Export missing Popper constants. We're at a crossroads here: either we just add a few missing exports (easy peasy) because existing apps already reach into private paths for them or we say, "Wait, hang on a minute, Popper needs a wholesale refactor so we should not let the interface grow now given we expect it to change soon." | ||
Any | a11y for MultiSelect | ||
https://folio-org.atlassian.net/browse/STCOR-603 and https://folio-org.atlassian.net/browse/FOLIO-1007 | Not ready | Not ready for review | |
Access to Help documentation based on FOLIO tenant version | Not ready | ||
Refactor old components away from deprecated React lifecycle methods, | Any | ui-calendar issues are not applicable as a new calendar app is in development. | |
Loosen @formatjs/cli dep after 4.6.x is patchedhttps://folio-org.atlassian.net/browse/STRIPES-774 | Any | ||
un-pin axe-core from 4.3.3 after 4.3.5 is released https://folio-org.atlassian.net/browse/STSMACOM-546 | Denys/Spitfire | ||
replace stripes-logger with categorical-logger https://folio-org.atlassian.net/browse/STRIPES-762 | Any | ||
Correctly label numbers in translation values as such https://folio-org.atlassian.net/browse/FOLIO-3233 | Any | ||
Fix inconsistent peer-deps | All | ||
Update any/all apps to current major version of eslint-config-stripes, and correspondingly migrate to @babel/eslint-parser and eslint 7.0.0. | All | ||
Kill redux-form. Kill it with fire. https://folio-org.atlassian.net/browse/UXPROD-2266 | Any | Remaining issues | |
stripes-cli and stripes-webpack should just use stripes-dev-server to serve instead of pulling in additional depshttps://folio-org.atlassian.net/browse/STCLI-166 | Thunderjet | ||
Update apps' plugin and components dependencies: ui-inn-reach | @Igor Godlevskyi (Deactivated) | ||
Update apps' plugin and components dependencies: ui-courses | Any | ||
Update apps' plugin and components dependencies: ui-quick-marc | @Denys Bohdan | Done? | |
Update your direct/in-development dependencies per repo | All | Use https://folio-org.atlassian.net/browse/FOLIO-3477 as a template | |
Results List: Change pagination for consistency | | ||
Results List: Change to hyperlink one row | Any | Change has been implemented MARC authority app and Users app | |
Apply basic keyboard shortcuts to app | Not ready | Need to provide a list | |
Spike: Investigate a way to generate interface for UAT. | Not ready | ||
Results list: Hierarchical layout POC | Not ready | ||
Storybook updates | Not ready | @John Coburn what should be updated? | |
Allow user/customer to specify app display order | Not ready | ||
Accessibility testing (automated) | To be discussed | ||
Apply Agreement MCL display updates across all FOLIO apps? | To be discussed | | |
Change record log tracker | To be discussed | Q: Do we store all updates to a record including who made the update and what? If so, can this be a UI only project? A: No, we do not. In most cases we store only the creator-id and create-datestame and the updater-id and update-datestamp. Loans are a counter example where we store a comprehensive changelog, but that wasn't handled with generic "audit-log" behavior; it is implementation specific. | |
Customize help link URL https://folio-org.atlassian.net/browse/STCOR-621 | Any | Allow override of help-icon URL via a value in stripes.config.js. |