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 - Zak will create a UXPROD feature
- Each team will create JIRAs to feature
- KG: Will create a wiki page related to stripes issue
|
|
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 | - For those that remain 10, at least set to 50 and work with Kimie on potential UI update based on scenario.
- New default should be 50.
- Note that 10 is the default when no limit clause is present. Thus, unless a query retrieves single record by ID, every query should include a limit clause.
Next steps: - Option 1: ask RMB to change the default value OR spring?
- Option 2: ask to do on run.
- Lets Proceed: Option 3:
- Zak will create a UXPROD
- Each team will create a story to audit
- Apply a limit clause to increase limit to 2000 ASK POs/QA to validate more than 10
- If stripes issue - create a story and assign to Stripes Force development
|
|
RTL/JEST > Prokopovych tests backlog | | Anton Emelianov (Deactivated) will work with teams to break up work across the following teams: Volaris, Spitfire, Thunderjet, Folijet * ui-inventory: https://issues.folio.org/browse/UXPROD-3322 * ui-users: https://issues.folio.org/browse/UIU-2257 |
|
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 | Volaris? 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 | AnyNeeds PO analysis | - Orders app supports print order lines and orders. There has been a request to support printing detail records across all apps. Can we the Orders app implementation become available at the stripes level and thus the standard for all apps? Thoughts Mikita Siadykh
- Are we confident ctrl-p/cmd-p is insufficient here, I mean, once we resolve STCOM-975 (below)?
|
|
Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-975 |
---|
|
| AnyThunderjet | 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 - Agreement on when to move the user from search pane to results list pane
- When a user clicks on a result then shift focus to the third pane
- Focus when a user creates a new record
- Focus when a user edits a record
|
|
Refactor infotip component Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-681 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-722 |
---|
|
| Any | Infotip must be updated to address accessibility issues. |
|
Refactor Timepicker component Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-326 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-694 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-568 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-569 |
---|
|
| Any | Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-326 |
---|
|
- is this still needed? DB: I thought we were refactoring in favor of "stripes-final-form" JC: Our 'form field' wrapper maps the props provided by React-final-form/Redux form to the props of the component. |
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-647 |
---|
|
| Any | Expose Ref to control in `<Selection>` and `<Select>` |
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-882 |
---|
|
| Any | MetaSection should correctly display unknown user values as "Unknown", not "System user" |
|
Create new Interactors Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-785 |
---|
|
| 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 - That is helpful to a new developer
- Is out-of-date
- That is critical and needs an update badly
|
|
Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STSMACOM-453 |
---|
|
| 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. |
|
Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-979 |
---|
|
| 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." |
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOM-977 |
---|
|
| Any | a11y for MultiSelect |
|
Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOR-603 |
---|
|
and Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | FOLIO-1007 |
---|
|
| Not ready | Not ready for review |
|
Access to Help documentation based on FOLIO tenant version Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCOR-591 |
---|
|
| Not ready |
|
|
Refactor old components away from deprecated React lifecycle methods, Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STSMACOM-624 |
---|
|
| 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 Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STRIPES-774 |
---|
|
| Any |
|
|
un-pin axe-core from 4.3.3 after 4.3.5 is released Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STSMACOM-546 |
---|
|
| Denys/Spitfire |
|
|
replace stripes-logger with categorical-logger Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STRIPES-762 |
---|
|
| Any |
|
|
Correctly label numbers in translation values as such Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | FOLIO-3233 |
---|
|
| Any |
|
|
Fix inconsistent peer-deps Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STRIPES-676 |
---|
|
| 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. Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STRIPES-742 |
---|
|
| All | |
|
Kill redux-form. Kill it with fire. Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-2266 |
---|
|
| Any | Remaining issues |
|
stripes-cli and stripes-webpack should just use stripes-dev-server to serve instead of pulling in additional deps Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STCLI-166 |
---|
|
| Thunderjet |
|
|
Update apps' plugin and components dependencies: ui-inn-reach plugin-find-user stripes-data-transfer-components
| Igor Godlevskyi (Deactivated) |
|
|
Update apps' plugin and components dependencies: ui-courses plugin-create-inventory-records | Any |
|
|
Update apps' plugin and components dependencies: ui-quick-marc stripes-acq-components | | Done? |
|
Update your direct/in-development dependencies per repo | All | Use Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | 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. |
|