...
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. | |||||||||||||||||||||||||||||||||||||||||||||
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 |
| |||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||
Setup and execute e2e automated tests for Vega team | Volaris? | Vega team needs assistance with smoke automated tests I believe. Anton Emelianov (Deactivated) and Oleksii Petrenko can you figure it out? | |||||||||||||||||||||||||||||||||||||||||||||
Create <<ui-module>>Dashboard widget (Dashboard Use Cases) | Not ready | Need requirements | |||||||||||||||||||||||||||||||||||||||||||||
Print a detail record | Any |
| |||||||||||||||||||||||||||||||||||||||||||||
| Any | We inadvertently broke detail-pane printing in STCOM-872 and need to restore it. | |||||||||||||||||||||||||||||||||||||||||||||
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
| Any | Infotip must be updated to address accessibility issues. | |||||||||||||||||||||||||||||||||||||||||||||
Refactor Timepicker component
| Any |
| |||||||||||||||||||||||||||||||||||||||||||||
| 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". Does the story have all details? It does, but they may not be clearly stated. | |||||||||||||||||||||||||||||||||||||||||||||
| 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 | |||||||||||||||||||||||||||||||||||||||||||||
| 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 patched
| Any | ||||||||||||||||||||||||||||||||||||||||||||||
un-pin axe-core from 4.3.3 after 4.3.5 is released
| Denys/Spitfire | ||||||||||||||||||||||||||||||||||||||||||||||
replace stripes-logger with categorical-logger
| Any | ||||||||||||||||||||||||||||||||||||||||||||||
Correctly label numbers in translation values as such
| 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.
| Any | Remaining issues | |||||||||||||||||||||||||||||||||||||||||||||
stripes-cli and stripes-webpack should just use stripes-dev-server to serve instead of pulling in additional deps
| 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 | Done? | ||||||||||||||||||||||||||||||||||||||||||||||
Update your direct/in-development dependencies per repo | All | Use
| |||||||||||||||||||||||||||||||||||||||||||||
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. |
...