**CUAL UPDATES**

Improved error message logic for interference section to prevent premature alerts.

MV-EXPInter TSTS BG QNT | Interference Error Message Logic

Ensure error messages on the Interference section are only displayed when both relevant fields have been interacted with, preventing premature visual noise. Currently, the error message "An Interference must have an Interfering Substance and Allowable Error %" appears prematurely when a new interference row is added. The error message should only be triggered whenboth fields have been interacted with (touched) but left blank. Leaving the "Interfering Substance" field blank should not trigger an error. h2. *Implementation Details:* # Update the validation logic for the Interference section: #* The error message is only triggered when both fields are touched and left blank. # Ensure the form validates correctly on save, ensuring that: #* An error message appears if any of the 2 fields are left empty, regardless of either field's state. h2. *User Flow:* # The user adds a new interference row. # No error message is displayed initially, even if both fields are empty. # The error message only appears when either field is touched but left blank.

Fixed validation error preventing test saving despite correct Range Low and Range High values.

MV-EXP TSTS QNT | Range Low and Range High Errors During Test Editing

The application displays a validation error message, *“Range low must be less than range high”*, and prevents saving a test, even when the entered values satisfy the condition (i.e., _Range Low_ is indeed less than _Range High_). !2025-01-21_173047_Microsoft_Edge.png|thumbnail! h4. *Steps to Reproduce* # Open the test setup or experiment configuration page. # Enter a valid *Range Low* and *Range High* value where _Range Low_ is less than _Range High_ (e.g., Range Low = 2.4, Range High = 186.2). # Attempt to save the test.

Updated the "Save" button to enable only when changes are made in the Method Comparison settings.

MV-EXP MV-EXPMC SMQ | Save Button Enabled Only on Change

Ensure that the "Save" button is only enabled if there are changes made in the Method Comparison (MC) experiment settings modal. Currently, the "Save" button in the *MC Experiment Settings* modal remains enabled regardless of whether there have been changes to the input fields. To enhance the user experience and prevent unnecessary submissions, the "Save" button should only become enabled when changes are detected in any of the fields. h2. User Flow: # User opens the *MC Experiment Settings* modal. # By default, the *Save* button is disabled. # If the user edits any of the fields (e.g., *Min. Samples*), the *Save* button becomes enabled. # If the user reverts all fields to their original values, the *Save* button is disabled again. # On clicking the *Save* button, it will be disabled once changes are saved successfully.

Fixed the missing yellow check icon for incorrect daily run results in SMQ and Qualitative modes.

MV-EXPPrec BG QL SMQ | Yellow Check Icon Missing for Incorrect Daily Run Results in SMQ & Qualitative Modes

Ensure that the yellow check icon appears correctly when all run results in a day are incorrect for SMQ and Qualitative modes in the Precision Experiment. The Precision Experiment UI currently has a bug where the yellow check icon does not display when all run results in a day are incorrect in SMQ and Qualitative modes. Instead, the field remains blank. This behavior is inconsistent with Quantitative mode, where the icon functions correctly. !yellow check.png|width=745,height=580,alt="yellow check.png"! h2. Steps to Reproduce: # Open the Precision Experiment for SMQ or Qualitative mode. # Input incorrect run results for all runs in a single day. # Observe that the yellow check icon does not appear in the daily summary column.

Updated "Result" label to "Carryover (%)" and added tooltips for clarification in the MV Carryover Percent Mode.

MV-EXPCarry ADT | Update Label in MV Carryover SD Mode Experiment Results

In the MV Carryover Percent Mode, the label currently displays "Result" for the final value. To align with the display in Percent Mode, this label should be updated to "Carryover (%)." Additionally, tooltips should be added to provide further clarification on the terms "Low Diff." and "Carryover (%)." !Screenshot 2024-11-07 at 10.39.23 AM.png|width=1016,height=90,alt="Screenshot 2024-11-07 at 10.39.23 AM.png"! h2. Implementation Details: # Update the label "Result" to "Carryover (%)" in the MV Carryover Percent Mode display. # Add a tooltip for "Low Diff." with the text: "The subtracted difference between the average of High-Low and Low-Low results." # Add a tooltip for "Carryover (%)" with the text: "Measure of how much a high concentration sample influences the result of a subsequent low concentration sample." h2. User Flow: # The user navigates to the MV Carryover Percent Mode. # The user changes the experiment mode to Percent. # The user observes the updated label "Carryover (%)" in place of "Result." # When hovering over "Low Diff.," a tooltip appears with the text: "The subtracted difference between the average of High-Low and Low-Low results." # When hovering over "Carryover (%)," a tooltip appears with the text: "Measure of how much a high concentration sample influences the result of a subsequent low concentration sample."

Updated the percent status to reflect changes in real time for tests in QNT/QL.

MV-EXP BG | The percent (%) status under Select Test should be updated in real time

Test Condition: User is in QNT/QL Steps to Replicate: # Inside a test, update any data in the test # Click save button Result: Notice that the percent result is not being updated. Still need to hit refresh button for the percent to be updated Screen recording: [https://jam.dev/c/57758ca8-fd6b-4e12-8936-46a9852ef8ba|https://jam.dev/c/57758ca8-fd6b-4e12-8936-46a9852ef8ba|smart-link]

Fixed save option not triggering when switching to TEa mode and force passing a sample.

MV-EXPMC MV-EXPTrueness QNT QL BG | Switching Regression to TEa mode doesn't trigger save with Force Pass

When switching from MC Regression Mode to TEa Mode, Force Passing a sample does not trigger the Save option as expected. !2024-12-18_083442_Microsoft_Edge.gif|width=1040,height=1168,alt="2024-12-18_083442_Microsoft_Edge.gif"! h2. *Steps to Reproduce:* # Navigate to a Method Comparison or Trueness experiment. # Switch from Regression Mode to TEa Mode. # Force Pass a sample. # Observe the Save button. [https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|smart-link]

Removed the display of Test and Experiment values when their sections were already shown.

MV-EXP BG | Test and Experiment value should not be displayed if the Select Test and Select Experiment section is already displayed

(This is quite hard to replicate) Ref: [https://discord.com/channels/965551040890028062/1219085471557353652/1303573129146138717|https://discord.com/channels/965551040890028062/1219085471557353652/1303573129146138717|smart-link] !image-20241106-055428.png|width=1174,height=1102,alt="image-20241106-055428.png"!

Disabled saving if only spaces are entered in the Example Precision Experiment Summary.

MV-EXP SMQ BG | User should not be able to save the changes if the entered data is space only

Environment: Dev Test Condition: User is in Templates > Edit Example Precision Experiment Summary Steps to Replicate: # In Example Precision Experiment Summary, enter three space # Click Save button

Fixed incorrect label in Precision Report Summary from "Result 2" to "Result 1."

MV-EXPPrec BG SMQ | Incorrect Result label displayed in Precision Report Summary

In the *SMQ Precision* experiment report, the summary section incorrectly displays *"Result 2"* for all samples. The correct label should be *"Result 1"* as per the experiment setup. !1.png|width=1437,height=853,alt="1.png"! !2.png|width=1438,height=774,alt="2.png"! h2. *Steps to Reproduce:* # Navigate to a *SMQ Precision* experiment with multiple samples. # Generate the experiment report by clicking on *Export PDF*. # Check the summary section in the report.

Adjusted menu tooltip positioning upon window resizing to ensure visibility.

ORGS BG | If the window is resized and upon hover, the menu tooltip should be on the tap of the page content

Steps to replicate: # Resize the window # Hover on the menu Result: Menu label is not visible *Second scenario:* The tooltip is cropped !image-20241114-004522.png|width=1254,height=906,alt="image-20241114-004522.png"! !image-20241106-034445.png|width=1513,height=982,alt="image-20241106-034445.png"!

Fixed the progress indicator for SMQ tests to show accurate completion percentages.

MV-EXP BG SMQ | Progress Indicator Always Shows 0% for SMQ Tests

Fix the progress indicator for SMQ tests to accurately reflect the percentage of test completion. The progress indicator for SMQ tests always displays "0% complete," even when there is measurable progress on the test. This issue creates confusion for users tracking the status of their tests. !zero.png|width=583,height=395,alt="zero.png"! h2. Steps to Reproduce: # Open an SMQ test in the MV module. # Perform some test steps to make progress. # Observe that the progress indicator remains at "0% complete."

Updated the Carryover Percent calculation formula for MV Carryover Experiments to ensure accurate results.

MV-EXPCarry ADT | Correct Calculation Formula for Carryover Percent in MV Carryover Experiment

The current formula for Carryover Percent is incorrect. The calculation should follow the formula: Carryover Percent=[(LowDiff/(High-LowLow)]X100 See this Example: !Screenshot 2024-11-07 at 11.33.27 AM.png|width=399,height=229,alt="Screenshot 2024-11-07 at 11.33.27 AM.png"! where: * *Low Diff* is calculated as the difference between *High-Low*​(The Low Rep directly after the last High Rep) and *Low-Low*(Average of Low-Low results) Low Diff: 3.30 - 3  = 0.3 * *High, 23.5,* is the average of the high results (24, 23.5, 23). * *LowLow, 3,* is the average of the low results (3, 3). The calculation should be as follows: Carryover Percent = [0.3/(23.5-3)]100 = [0.3/(20.5)]100 =[0.01463415]100 =1.46% h2. Implementation Details: # Update the Carryover Percent calculation formula in the MV Carryover Experiment to use the corrected formula. # Ensure that the updated calculation is reflected accurately in all relevant sections where Carryover Percent is displayed. h2. User Flow: # The user conducts the MV Carryover Experiment in Percent Mode. # The user views the updated Carryover Percent, which now reflects the correct calculation.

Updated icons in the Results Banner for "Incomplete" and "Not Started" states to enhance clarity.

MV-EXPInter TSTS QNT | Update icons for Incomplete/Not Started states in Results Banner

To improve clarity in the Results Banner by replacing the current yellow checkmark icon for "Incomplete" and "Not Started" states with the three dots icon, ensuring consistency and better visual representation. Currently, the Results Banner uses a yellow checkmark icon for experiments marked as "Incomplete" or "Not Started," which may confuse users as the checkmark implies progress or completion. Updating these states to use the three dots icon will align them with user expectations and clearly indicate that the experiment is pending or incomplete. !image5.png|width=796,height=542,alt="image5.png"! !image4.png|width=351,height=65,alt="image4.png"!

Fixed inconsistency in undo/redo actions when using Force Pass in Method Comparison experiments.

MV-EXPMC MV-EXPTrueness QNT QL BG | Undo/Redo states inconsistent with Force Passing options

The undo/redo states behave inconsistently when using the Force Pass option in the Method Comparison experiment. * *Issue:* The "Undo All" option is available, but standard Undo and Redo actions are not functional when interacting with Force Passing. !2024-12-18_083124_Microsoft_Edge.gif|width=1040,height=728,alt="2024-12-18_083124_Microsoft_Edge.gif"! h2. *Steps to Reproduce:* # Navigate to a Method Comparison or Trueness experiment. # Force Pass a sample by double-clicking the icon. # Attempt to use the Undo/Redo buttons. [https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|smart-link]

Removed unnecessary space appearing below the "Verification" and "Analyzer" buttons in the sidebar.

ORGS BG | When clicking the Verification and Analyzer in the sidebar, space below the "Verification" or "Analyzer" should not be displayed

*Test Condition:* User is in [https://staging.cualia.io/org/Tl2p0u9W/mvs|https://staging.cualia.io/org/Tl2p0u9W/mvs] *Steps to replicate:* # Click Dashboard # Click Verifications # Click Departments # Click Analyzers *Screen recording*: [https://jam.dev/c/37880f93-42be-4a47-951d-0b3c816db22a|https://jam.dev/c/37880f93-42be-4a47-951d-0b3c816db22a|smart-link] *Result*: Upon clicking Verifications and Analyzers button, a space will appear below the buttons

Fixed icon positioning; undo, redo, and reset icons remained stable after clicking redo button.

MV-EXP MV-EXPMC SMQ BG | The undo, redo and reset icons should not move upon clicking redo button

Environment: Staging Test condition: User is in [https://staging.cualia.io/org/Tl2p0u9W/mv/f1n5k0426x/tests/hh6uy6xr8xk/semiQuant/methodComparison|https://staging.cualia.io/org/Tl2p0u9W/mv/f1n5k0426x/tests/hh6uy6xr8xk/semiQuant/methodComparison] Steps to replicate: # Update the source of Label one, label two and label three # Click undo button # Click Redo button Result: Undo, redo and reset icons moved on the left side upon clicking Redo button

Made the "Run Order" column uneditable in MV Carryover experiments to ensure consistent sequencing.

MV-EXPCarry ADT | Make "Run Order" Column Non-Editable in MV Carryover Experiment

In the MV Carryover experiment, the "Run Order" column currently allows edits. This ticket proposes making the "Run Order" column hardcoded and non-editable to maintain consistent ordering across experiments. This will prevent accidental changes to the run sequence, ensuring clarity and uniformity. !Screenshot 2024-11-07 at 1.49.13 PM.png|width=1063,height=820,alt="Screenshot 2024-11-07 at 1.49.13 PM.png"! h2. Implementation Details: * The "Run Order" column should be hardcoded with predefined values (e.g., High Rep 1, High Rep 2, High Rep 3, Low Rep 1, Low Rep 2). * Disable editing permissions for this column for all user roles. * Ensure this change applies to both existing and new MV Carryover experiments. h2. User Flow: # User opens the MV Carryover experiment interface. # The "Run Order" column displays a fixed sequence without the ability to modify entries. # Users can view but not edit the sequence in the "Run Order" column.

Fixed issue where dropdown options appeared after adding a unique Analyte in the Quantitative Test modal.

ANZ BG | In analyzers, when adding a Analyte in Add Quantitative Test modal, If I entered the Analyte and I clicked the Add button, the dropdown options should not be displayed.

Test Condition: User is in [https://app.cualia.io/org/gnxnzhnh57j/analyzer/g19zft1ylf/tests/qual|https://app.cualia.io/org/gnxnzhnh57j/analyzer/g19zft1ylf/tests/qual] User is QA Owner Steps to replicate: # In Tests Quant, click Add a Test button # Input a unique or new Analyte Name e.g. TAN000000 # Click Add: [Name of Analyte] Result: Dropdown options were displayed Screen recording: [https://jam.dev/c/3b1a2cd5-8f25-4990-86a2-dfbc35f3d928|https://jam.dev/c/3b1a2cd5-8f25-4990-86a2-dfbc35f3d928|smart-link] Note: This is also applicable to QL

Fixed the status display in Experiment Result to show In Progress instead of Not Started.

MV-RPRT | Correct status should be displayed in Experiment Result

*Environment:* Dev *Test Condition:* int1: Failed int2: Incomplete int3: Not Started User is in: [https://dev.cualia.io/org/Tl2p0u9W/mv/syreqq5kxm/report/preview/experiments?testId=3yb4qnmspr5&expKey=interference|https://dev.cualia.io/org/Tl2p0u9W/mv/syreqq5kxm/report/preview/experiments?testId=3yb4qnmspr5&expKey=interference] In Experiment Result, status displayed is Not Started wherein it should be In Progress

Updated the label from "Result" to "Carryover SD" in MV Carryover Experiment results for clarity.

MV-EXPCarry ADT | Update Label in MV Carryover SD Mode Experiment Results

The current display of results in the MV Carryover (SD Mode) Experiment section shows "Result" as the label for the bottom results. To better align with the terminology used in this experiment, this label should be changed to "Carryover SD." !Screenshot 2024-11-07 at 10.19.58 AM.png|width=1123,height=87,alt="Screenshot 2024-11-07 at 10.19.58 AM.png"! h2. User Flow: # The user navigates to the MV Carryover Experiment. # The user changes the experiment mode to Standard Deviation (SD). # They observe the updated label "Carryover SD" where "Result" previously displayed.

Corrected table rows to remove status icons where data was missing, resolving confusion in experiment reports.

MV-RPRT QNT BG | Table Rows Without Data Display Icons and Sticky Results not Updating

In the experiment report, table rows without data are incorrectly displaying status icons (e.g., checkmarks or X marks). Rows with empty data should not display any icons, as this creates confusion and misrepresents the results. More issues found by developer(see comments). *Steps to Reproduce:* # Navigate to the *Method Verification Report* section. # Generate a report for a quantitative experiment. # Observe the *tables* in the report where some rows do not have data in the "Source" or "Actual" columns. # Notice that these rows still display icons in the status column. # Results greater than or equal to 3 will just show as a negative sign (-). # Results section doesn’t stick. # There are icons even if there is no data in the cells.

Fixed missing reference values in the SMQ Precision report PDF for samples.

MV-EXPPrec BG SMQ | Missing Reference Value in SMQ Precision Report PDF

In the *SMQ Precision* experiment report PDF, the *Reference Value* field is blank in the *Samples* section. This field should display the correct reference value associated with each sample as defined in the experiment setup. !3.png|width=692,height=612,alt="3.png"! h2. *Steps to Reproduce:* # Navigate to an *SMQ Precision* experiment. # Generate the experiment report by clicking on *Export PDF*. # Check the *Reference Value* column in the *Samples* section of the PDF.

Result Types: Qualitative and Quantitative MV Experiments: Method Comparison and Trueness A double click action on the green checkmark (eligible samples only) will set the result to pass regardless of the Error Index. This facilitates many tests where values in specific ranges do not follow the requirements around other ranges. The green ✅  checkmark will turn a lighter shade of green to indicate that it is force-passed without a strong negative aesthetic.

❗️MV-EXP ADT | Implement Force Passing of Results in MV-EXPMC QNT QL and MV-EXPTrueness QNT and QL

We will add forcepassing of results. This is because we’re doing a test where the allowable error is that actual and reference that are both below 100 are a pass. This makes using TEa’s awkward. As a user we want to allow the user to force pass a sample. Modify the existing column with the check (✅) and cross (❌) icons in the results table to support Force Pass functionality, allowing users to mark specific samples as "always pass" under defined conditions. [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-163421&t=fRFYuXpSzyddcMjH-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-163421&t=fRFYuXpSzyddcMjH-4|smart-embed] See the last column of row 3 in the Figma above. h2. *Implementation:* # *Update Existing Column*: #* Modify the existing check (✅) and cross (❌) icons in the last column of the results table to include Force Pass functionality. # *Edit Mode Behavior*: #* Feature is only accessible in *Edit Mode* (not in read-only mode). #* Mouse changes to a pointer cursor when hovering over the icons. #* Tooltip on hover in Edit Mode: #** Default state: _“Force Pass: double click the icon to set this sample to always pass.”_ #** When Force Passed: _“Sample is set to Force Pass when eligible. Double click to remove.”_ # *Non-Edit Mode Behavior*: #* Tooltip on hover: _“Sample has been set to Force Pass.”_ # *Double-Click Functionality*: #* *Force Pass Action*: #** On double-click of a ❌ or ✅: #*** Icon opacity changes to *65%*. #*** Sample is set to *always pass*, regardless of the error index (-1 to 1) or edits. #*** Force Pass persists even if the sample becomes ineligible but will reactivate if eligibility is restored. #* *Remove Force Pass*: #** On double-click of a Force Passed sample, the Force Pass state is removed, and the icon reverts to its original state. # *Eligibility Handling*: #* Force Passed samples are not included in calculations if they become inel

When in an MV, the Analyzer name in left side navigation now has a button to return to the analyzer.

MV-EXP | Add "Go to Analyzer" Icon Button

Add an icon button in the MV navigation that allows users to open the associated analyzer in a new window for quick access. !2024-12-05 140203 Microsoft Edge.png|width=530,height=690,alt="2024-12-05 140203 Microsoft Edge.png"! h2. *User Flow* # User navigates to the MV section. # The "Go to Analyzer" icon button is visible in the MV navigation bar. # User clicks the button. # The analyzer details page opens in a new browser window or tab.

Fixed a bug where a deleted tests would still show up in the analyzer for a few minutes.

TSTS ADT | Ghost of Deleted or Edited Test in Analyzer Test List

Fix the issue where deleted or edited tests briefly appear ("ghost") in the analyzer test list after deletion or editing. Ensure the redirect only occurs after the API call is successfully completed. When a test is deleted or edited, the user is redirected back to the analyzer test list. However, the deleted or edited test briefly appears in the list before the update is reflected, causing confusion. This occurs because the redirect happens before the API call completes. h2. *Steps to Reproduce* # Navigate to the analyzer test list. # Delete or edit a test. # Observe the brief presence ("ghost") of the deleted or edited test in the list after redirection.

In the MV Method Comparison and Trueness experiment table headers, the “Source” column header was renamed to “Comment”. This was to help provide flexibility to put whatever supplementary information is required such as source, date, operator or general commentary.

❗️MV-EXP ADT MV-EXPMC MV-EXPTrueness QL QNT | Update Column Header Text in Experiments and Exported Files

Update the column header text from “Source” to “Comment” across the following areas: # Method Comparison (MC) Experiments. # Exported XLSX, CSV, and PDF files. The column header labeled as “Source” needs to be changed to “Comment” for consistency and clarity. This change should apply to all relevant sections, including both the experiment UI and exported files. The updates will apply to both Quantitative (QNT) and Semi-Quantitative (QL) methods, specifically for Method Comparison (MC) and Trueness experiments. h2. *Implementation Details:* # *UI Changes:* #* Locate the “Source” column in the experiment table within the MC experiments. #* Update the header text to “Comment.” !Screenshot 2024-12-05 at 1.55.10 PM.png|width=1586,height=767,alt="Screenshot 2024-12-05 at 1.55.10 PM.png"! # *Export Changes:* #* Ensure the “Source” column in exported XLSX, CSV, and PDF files reflects the new header text “Comment.” #* Confirm this change applies to all relevant exportable formats. [^MCV_semiQuant.xlsx] # *Affected Experiments:* #* QL QNT Method Comparison (MC). #* QL QNT Trueness experiments.

Whenever you start a new MV without a template, the defaults will be set to the reports: Header Title: Analyzer Information Header Subtitle: Department Name Footer Line 1: Evaluator Footer Line 2: Date the MV Started

MV-RPRT ADT | Default Report Values on MV Creation

Set default values for report headers and footers upon MV creation. These values may be hardcoded to ensure consistency and ease of implementation. When a new MV is created, default values for the report headers and footers should automatically populate. This will save time and ensure uniformity across reports. The default values may be hardcoded but should pull dynamically from the relevant properties. !2024-12-05 134534 Microsoft Edge.png|width=1219,height=350,alt="2024-12-05 134534 Microsoft Edge.png"! h2. *Default Values* # *Header Title:* {{{analyzer.name} {analyzer.identifier} MV}} # *Header Subtitle:* {{{department.name}}} # *Footer Line 1:* {{Evaluated by: {mv.createName}}} # *Footer Line 2:* {{Date Started: {mv.createdDate in YYYY-MM-DD format}}} h2. *Implementation Details* # *Default Population Logic:* #* Populate the default values during MV creation. #* Values may be hardcoded and should dynamically map to the relevant fields. # *Formatting Requirements:* #* Ensure the date format is strictly {{YYYY-MM-DD}}. #* Use dynamic placeholders to pull values from the respective properties: #** {{{analyzer.name}}} and {{{analyzer.identifier}}} from the analyzer. #** {{{department.name}}} from the department associated with the MV. #** {{{mv.createName}}} from the creator's name. #** {{{mv.createdDate}}} from the creation timestamp. # *UI/UX Considerations:* #* Display these values in their respective fields on the report preview or editor. #* Allow users to manually edit these values if needed after creation.

Share and invitation emails will no longer be case sensitive. This was causing invitations to not be sent.

GLBL RLS DV | Case Sensitivity Bug in Emails for Shared Invites and Authentication

Fix the issue where email addresses in shared invites, invite emails, and authentication registration workflows are treated as case-sensitive, causing mismatches and access issues. !2024-12-05 115446 Microsoft Edge (1).png|width=600,height=632,alt="2024-12-05 115446 Microsoft Edge (1).png"! Emails currently require an *exact match*, including case sensitivity, when inviting, sharing, or authenticating. For example: * If an invite is sent to {{Calvin@cualia.io}}, users cannot access the shared resource with {{calvin@cualia.io}}. This behavior is inconsistent with standard email handling, where addresses are typically case-insensitive. h2. *Steps to Reproduce* # Send an invite to a user with an email address using uppercase letters (e.g., {{Calvin@cualia.io}}). # Attempt to log in or authenticate using the lowercase version of the email (e.g., {{calvin@cualia.io}}). # Observe that access is denied due to a mismatch. h2. *Implementation Details* # *Normalization Fix*: #* Normalize email addresses (convert to lowercase) before storing them in the database. # *Affected Workflows*: #* Shared invites #* Invite emails #* Authentication registration emails # *Database Update*: #* Normalize existing email records in the database, if feasible. # *Validation*: #* Apply input sanitization to remove unnecessary whitespaces.

In MV Previews, selecting the export to PDF button will download the PDF with a set naming convention to match what is being viewed on the PDF preview.

MV-RPRT ADT | Dynamic PDF Export Filename Based on Context

Ensure PDF exports are named dynamically based on the context of selected tests and experiments, providing meaningful and user-friendly filenames. The current export filenames do not reflect the specific content of the exported report. This task standardizes filenames for exports, improving clarity and usability by reflecting the selected analyzer, tests, and experiments. h2. *Filename Rules:* # *All Tests and Experiments:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - All Experiments}} # *One Test’s Experiments:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {test.nameAbbrev}}} # *One Experiment from All Tests:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {experiment.name}}} # *One Test and One Experiment:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {test.nameAbbrev} {experiment.name}}} h2. *Implementation Details* # *Dynamic Filename Logic:* #* Implement a function to determine the appropriate filename format based on the selection context. #* Retrieve the necessary data from the selected analyzer, test, and experiment. # *Integration Points:* #* Update the export process to include the dynamic filename generation before saving the PDF. # *Validation and Fallbacks:* #* Ensure all variables ({{{analyzer.nameAbbrev}}}, {{{analyzer.identifier}}}, {{{test.nameAbbrev}}}, {{{experiment.name}}}) are properly populated. #* If any required data is missing, use a generic fallback filename, e.g., {{MV Export}}. # *Edge Cases:* #* Handle scenarios with incomplete selections or empty data gracefully, ensuring no errors in export functionality.

The test’s units were added to each header of the PDF exports as a reference for viewers.

MV-RPRT ADT | Add Units to All Experiment PDF Export Files

Ensure that units associated with a test are included in the exported PDF reports, enhancing clarity and alignment with experiment data. Currently, experiment exports in PDF format do not display the test units. This ticket aims to append the corresponding units (if they exist) to the right side of the *Experiment Design Title* for all exported PDF reports. !2024-12-05 130746 Microsoft Edge.png|width=867,height=204,alt="2024-12-05 130746 Microsoft Edge.png"! h2. *Implementation Details:* # *Condition:* #* Check if the test has units associated with it. #* If units exist, append them to the *Experiment Design Title*. #* If no units exist, the title remains unchanged. # *Placement:* #* The units should be appended on the right side of the *Experiment Design Title*, separated by a space or parentheses (e.g., "Experiment Design Title (mg/dL)"). # *PDF Export Update:* #* Update the PDF generation logic to dynamically include units in the title section of the exported report. #* Ensure proper formatting to maintain readability and consistency. h2. *User Flow:* # User initiates the export of an experiment in PDF format. # The system generates the PDF, dynamically appending units (if applicable) to the *Experiment Design Title*. # The exported PDF is downloaded or previewed, displaying the updated title with units.

When creating or editing a test, the analyte selection dropdown is now in alphabetical order.

TSTS ADT |  Analyte Dropdown Alphabetical Order on Test Creation

Ensure the Analyte dropdown in the Test Creation form is displayed in alphabetical order to improve usability and efficiency. Currently, the Analyte dropdown in the Test Creation form may not be sorted, making it difficult for users to locate specific analytes quickly. This task ensures that the list is presented in alphabetical order by default. !2024-12-05 140442 Microsoft Edge.png|width=523,height=434,alt="2024-12-05 140442 Microsoft Edge.png"!

Fixed an issue where the linearity chart was missing in PDF exports.

❗️MV-RPRT ADT BG | Export Missing the Graph

Fix the issue where the graph is missing from the exported files in the MV-EXPLin experiment results. Currently, when users export the results from the MV-EXPLin (Linear Regression) experiment, the graph section is not included in the export. This bug affects the ability to provide a complete report, as the graph is a critical part of the experiment's results. h2. *Steps to Reproduce* # Navigate to an MV-EXPLin experiment with results. # Ensure that the graph is displayed on the results page. # Click on the "Export" button. # Open the exported file (e.g., PDF or Excel). # Observe that the graph is missing from the export.

Add and Edit Department action buttons have been changed to “Add Department” and “Save.”

ORGS DEPS ADT | Update Department Edit CTA Buttons

Improve clarity and user experience by updating the CTA buttons in the Department section to reflect the action being performed (e.g., adding or editing a department). Currently, the CTA button for editing a department only displays "Edit," regardless of the action context. This ticket aims to update the button text to provide clear labels based on the user's current action: * *"Cancel"* and *"Add Department"* when adding a new department. * *"Save"* when editing an existing department. h2. *Implementation Details:* # *Adding a Department:* #* Display two buttons: #** *"Cancel"* - Cancels the action and reverts to the default Department page state. #** *"Add Department"* - Confirms the addition of a new department. # *Editing a Department:* #* Replace the current "Edit" button with a single *"Save"* button to save changes. # *General Behavior:* #* Ensure proper state management for the buttons to reflect the correct context (adding or editing). #* Provide visual feedback upon button click (e.g., loading indicator, state change). #* Retain accessibility features for all buttons. h2. *User Flow:* # User navigates to the Department section. # Clicks *"Add Department"* or selects a department to edit: #* If adding a department: #** *"Cancel"* and *"Add Department"* buttons are displayed. #* If editing a department: #** *"Save"* button is displayed. # User completes the action or cancels it, returning to the default Department page view.

A fix was made where the MV sharing mechanism for email input would stay within the text box even after submission.

MV-RPRT ADT BG | MV Sharing Email Should Disappear on Submit

Ensure that after the user submits an email address for sharing, the input field and any associated UI elements (e.g., email validation messages) disappear, providing clear feedback that the action was successful. Currently, when an email is submitted for sharing an MV, the input field remains visible, which could cause confusion about whether the email was sent successfully. !2024-12-05 114441 Microsoft Edge (1).gif|width=764,height=566,alt="2024-12-05 114441 Microsoft Edge (1).gif"! h2. *Steps to Replicate:* # User navigates to the *MV Sharing* page. # Enters an email address in the input field. # Clicks the *Submit* button. # Email still shown in email field. h2. *Implementation Details:* * After the "Submit" button is clicked and the email is successfully sent: ** Hide the email input field and associated elements. ** Display a success message confirming the email was sent. ** Ensure proper error handling if the submission fails (retain the input field in this case with an error message).

A return to MV button was added to the reports page to make it easier to return to the workspace.

MV-RPRT ADT | Go To MV Button in Report Section

Enable users to navigate back to the MV section from the Report section easily, ensuring seamless interaction for both standard and shared modes. Add a "Go To MV" button in the Report section. The button's behavior should adapt to the linking protocol based on whether the MV is in *Standard Mode* or *Shared Mode*. !Screenshot 2024-12-07 at 2.09.09 PM.png|width=253,height=461,alt="Screenshot 2024-12-07 at 2.09.09 PM.png"! h2. *Implementation Details* * *Button Placement*: Add the button to the header (or other prominent area) of the Report section for high visibility. * *Button Behavior*: ** *Standard Mode*: Link directly to the corresponding MV details page. ** *Shared Mode*: Follow the shared protocol to navigate to the appropriate shared MV details page. * *UI/UX Requirements*: ** The button text: "Go to MV". ** Design and style should align with existing navigation buttons. * *Additional Considerations*: ** Ensure the button is disabled if the navigation path cannot be determined. ** Display an appropriate error message if navigation fails. h2. *User Flow* # User is in the Report section. # User clicks on the "Go to MV" button. # Depending on the mode: #* *Standard Mode*: Redirect to the specific MV details page. #* *Shared Mode*: Redirect to the shared MV view, based on the shared protocol.

Result Types: Quantitative MV Experiments: Method Comparison In Quantitative Method Comparisons, an option to use R-Squared Linear Regression values as the acceptance criteria has been added. Use the Experiment Settings to switch to R-Squared regression as the acceptance criteria. You will be able to set a min. R-Squared value required to meet experiment requirements.

❗️MV-EXPMC ADT QNT | Linear Regression Acceptance Criteria

We are going to add a new acceptance criteria to Quantitative Method Comparison [https://www.notion.so/cualia/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658180989f81f92b5eb000fe?pvs=4#1521b48e6581807490bdfb9d81cbb7b3|https://www.notion.so/cualia/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658180989f81f92b5eb000fe?pvs=4#1521b48e6581807490bdfb9d81cbb7b3] h2. Important Note * Calculations are the same.The only difference is that we only base pass/fail on if the calculated R-Squared ≥ Acceptance Criteria R-Squared. This is already calculated in our math. * MC ONLY. NOT MV-EXPTRUENESS. h2. General Changes and Notes * *Line Chart*: Remove all TEa Lines. Only persist the linear regression line. ** Removed in PDF chart as well * *Remove Error Index Chart* ** Removed in PDF export as well * R-Squared results should have max 3 decimals h2. *Experiment Settings*: * New Regression Mode option * *Min. R-Squared field*: Same as the one on MV-EXPLin [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23603-206737&t=WxKwVPiPNrlJHhvz-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23603-206737&t=WxKwVPiPNrlJHhvz-4|smart-link] ** *Tooltip Adjustment on this field*: “R-Squared coefficient from calculating Linear Regression. Values above 9.95 are often deemed acceptable.” !2024-12-05 151706 Microsoft Edge.png|width=274,height=122,alt="2024-12-05 151706 Microsoft Edge.png"! h2. Results Table * Removed Bias and Error Index Column (there is no pass fail of individual results) [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-150091&t=fRFYuXpSzyddcMjH-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-150091&t=fRFYuXpSzyddcMjH-4|smart-link] h2. Results Section * Results Section should match the [Figma|https://www.notion.so/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658

In the analyzer’s list of quant, qual and semi-quantitative tests, the alignment of the name was fixed to be more readable.

MV EXP QL SMQ BG | The Name label should be properly aligned

Test condition: User is in [https://cualia-svelte-git-cmv-278-smq-cualia.vercel.app/org/Tl2p0u9W/analyzer/g4vibfj2n1/tests/qual|https://cualia-svelte-git-cmv-278-smq-cualia.vercel.app/org/Tl2p0u9W/analyzer/g4vibfj2n1/tests/qual] Test account: QA Owner Notes: Kindly properly align or align center the “Name” label Screen recording: [https://jam.dev/c/bf939ec5-e16d-4982-968a-a29e69179cf1|https://jam.dev/c/bf939ec5-e16d-4982-968a-a29e69179cf1|smart-link]

Added result options for SMQ tests created after the Method Validation.

ANZ TST SMQ BG | SMQ test added after MV is created should include Result Options

*To Replicate* # Use an analyzer to create an MV # In the organization's analyzer, add a SMQ test with result options # In the MV, load up the new SMQ test. Result options will not be available. !2024-12-03_083644_Microsoft_Edge.png|width=3406,height=1242,alt="2024-12-03_083644_Microsoft_Edge.png"! [https://discord.com/channels/965551040890028062/1313303425802440775/1313303431984709642|https://discord.com/channels/965551040890028062/1313303425802440775/1313303431984709642|smart-link]

Fixed search issue for verifications using File Name, Evaluator, and Analyzer ID.

MV BG | Unable to search for verification using File Name, Evaluator, and Analyzer ID

Steps to replicate: # Login to the app. # Navigate to Verifications. # Search for a Verification using the following: ## File Name ## Evaluator ## Analyzer ID !Searchbug.PNG|width=1179,height=491,alt="Searchbug.PNG"! [https://discord.com/channels/965551040890028062/1112699023552421938/1313315079646875699|https://discord.com/channels/965551040890028062/1112699023552421938/1313315079646875699|smart-link]

[Verifications] MV Experiment Printing

[Verifications] MV Experiment Printing

Place tooltips on each of the Performance Characteristics fields

Place tooltips on each of the Performance Characteristics fields

!Screenshot 2024-05-18 at 1.44.13 PM.png|width=1338,height=603,alt="Screenshot 2024-05-18 at 1.44.13 PM.png"!

MV - Update Verification Tables

MV - Update Verification Tables

Analyzer verifications - the last column doesn’t make sense. It should be last updated? Also is it consistent with !20240602-123858 - Microsoft Edge - Cualia.png|width=751,height=598,alt="20240602-123858 - Microsoft Edge - Cualia.png"!

LBS | Add, Edit, and Delete Laboratory

LBS | Add, Edit, and Delete Laboratory

This is the Epic for all tasks, bugs, and user stories related to the Adding, Editing, and Deleting of Laboratories.

20240516 Organization Audit Tickets p01

20240516 Organization Audit Tickets p01

These are the tickets associated with the 20240516 Organization Audit. Part 1 [http://app.noota.io/share-transcribe/N5kY4FFUsdTMMJmewZzUtoWZ1QFSEFD0TLdDOuo3aq5kMBRkT|http://app.noota.io/share-transcribe/N5kY4FFUsdTMMJmewZzUtoWZ1QFSEFD0TLdDOuo3aq5kMBRkT|smart-link] Part 2 [http://app.noota.io/share-transcribe/np1a0k2RIRjWzdmVLBXdwU1TzEzcZFU0NJJUbuMzaq5kMBRkT|http://app.noota.io/share-transcribe/np1a0k2RIRjWzdmVLBXdwU1TzEzcZFU0NJJUbuMzaq5kMBRkT|smart-link]

ORG - Organization Plan Features

ORG - Organization Plan Features

MV | Implementation of Sharing Functionality

MV | Implementation of Sharing Functionality

This is an epic that will handle all items and bugs related to the MV sharing capabilities of the app.

[Verifications] Test Experiment Summaries

[Verifications] Test Experiment Summaries

This is an epic that handles features and bugs related to Experiment Summaries.

ADT | 202407 Dev UX Audit

ADT | 202407 Dev UX Audit

h1. Context Calvin performed an audit of the app in preparation for launch in July 31. This Epic includes all the required changes prior to going live on July 31. Priorities are all that has the {{❗️}} mark. The audit is composed of 3 parts. They are all documented in this [notion page|https://www.notion.so/cualia/2024-07-DV-UX-Audit-0baa84b241ec498fa5bc198d37582cf4] together with the recording. All the parts of the audit are added in this single epic, to differentiate which ticket belongs to which part, a label has been added to each ticket. ||*Part*||*Label*|| |Part 1 Auth Org SomeMVSettings|{{202407-app-audit-p1}}| |Part 2 Quant MV Experiments|{{202407-app-audit-p2}}| |Part 3 Qual MV Experiments Reports Printing Sharing|{{202407-app-audit-p3}}|

Update deprecated sass import to sass use

Update deprecated sass import to sass use

DV | Create data-testids for automation

DV | Create data-testids for automation

DV | Users should have an option to use promo codes during checkout session

DV | Users should have an option to use promo codes during checkout session

h1. *Context* Currently, during checkout, there’s no way for a user to add a coupon. This will be needed in future to allow users to claim coupons for percent-off or amount-off promos, and is also needed for QA testing in production. h1. *Technical Details* * When a checkout session is created, we need to allow promotion codes. Check {{src/routes/org/[orgId]/settings/billing/subscription-plan/+page.server.ts}} , make sure {noformat}allow_promotion_codes: true{noformat}

❗️BG MV-EXPMC QNT | Quantiative Method Comparisons do NOT calculate the Error Indexes correctly

❗️BG MV-EXPMC QNT | Quantiative Method Comparisons do NOT calculate the Error Indexes correctly

Quantiative Method Comparisons do NOT calculate the Error Indexes. Issue is not occuring in dev. !Screenshot 2024-08-05 at 1.34.16 PM.png|width=1887,height=895,alt="Screenshot 2024-08-05 at 1.34.16 PM.png"! Expected Behavior: Attached in the video right side is dev Actual Behavior: Attached in the video left side !20240805-132711_-_Microsoft_Edge_-_0724_analyte_Method_Comparison_2024-07-29_new_analyzer_MedCity_-_Cualia.io.mov|width=2950,height=1374,alt="20240805-132711_-_Microsoft_Edge_-_0724_analyte_Method_Comparison_2024-07-29_new_analyzer_MedCity_-_Cualia.io.mov"! ALSO: change the default setting for Quant MC TEa Allowance Setting to be TEa instead of SEa. Same for the following: Precsion -> REa Trueness -> TEa

DV | Apply Supabase performance advisor recommendations

DV | Apply Supabase performance advisor recommendations

h2. Context Use the Database Performance and Security Advisors to check database for issues such as missing indexes and improperly set-up RLS policies. At the time of writing this ticket there are: * 0 errors * 94 warnings * 45 suggestions [https://supabase.com/dashboard/project/qxqipyssridfqjwmhcir/advisors/performance?preset=ERROR&id=|https://supabase.com/dashboard/project/qxqipyssridfqjwmhcir/advisors/performance?preset=ERROR&id=|smart-link] Requirement: * Apply fixes for performance warnings (only fix warnings that makes sense) and make sure all recommendations are applied. * New migration file should be created after ticket.

❗️ BG MV TSTS | When dividing 0/0, Error index should be 0 then passed

❗️ BG MV TSTS | When dividing 0/0, Error index should be 0 then passed

Sample 3 in this case is has an actual and reference of 0. In our calculations we're dividing 0/0 indeterminate in mathematics. Current Behavior it just shows blank and incorrect Expected behavior it should be zero and pass. !image-20240807-042012.png|width=827,height=752,alt="image-20240807-042012.png"! Team will have to think of a clever way to make sure all 0/0s will equal 0 and pass.

❗️ BG MV QNT QL | The TEa pool does not show up in a fresh MV

❗️ BG MV QNT QL | The TEa pool does not show up in a fresh MV

The TEa pool doesn't include TEas available for the Analyte. It's only when I reset the analyte and then pick the pooled analyte that the pool will be available. !20240805-134449_-_Microsoft_Edge_-_Edit_Hematocrit_2024-08-05_XN-350_Pathlab_Medical_Laboratories_-_Cualia.io.mov|width=1278,height=1374,alt="20240805-134449_-_Microsoft_Edge_-_Edit_Hematocrit_2024-08-05_XN-350_Pathlab_Medical_Laboratories_-_Cualia.io.mov"!

DV | Setup Eslint and Prettier

DV | Setup Eslint and Prettier

h2. Context We need to setup ESLint and Prettier to catch potentially problematic patterns and establish a standard formatting pattern in our project. Discuss with the dev team what needs to be added in the linter and prettier config. ESLint benefits: * Static code analysis helps in catching errors before runtime * Code consistency. Enforce consistent code style across our codebase Prettier benefits: * Code formatting * Reduced merge conflicts * Consistency across environments h2. Dev Notes: * After settings up ESLint, we might need to do a lot of refactoring (it depends on lint config we will setup). If the refactor is way too complex, we can create subtasks and work on them separately.

❗️ BG DV | The Billing Payment Method section in Billing Payment Method tab does not go to the Stripe Payment page

❗️ BG DV | The Billing Payment Method section in Billing Payment Method tab does not go to the Stripe Payment page

!Screenshot 2024-08-08 at 1.23.52 PM.png|width=1545,height=874,alt="Screenshot 2024-08-08 at 1.23.52 PM.png"! Steps to replicate: # Go to Profile then navigate to the Billing page. # Go to the Payment Method tab. # Click on either the Auto Renewal or Billing Payment Method section. # It does not go to the Stripe Payment page.

MV QNT QL BG | Free Users should not be able to activate more than 3 tests

MV QNT QL BG | Free Users should not be able to activate more than 3 tests

*Test Condition:* # Account is newly created # Account is in Free plan # User’s account has a newly created analyzer *Steps to Replicate:* # In Quant Tests, toggle off 1 test # Click refresh button # Go to Qual test, toggle on 1 test # Click refresh button

TSTS DV - TEas should be cloned on test creation

TSTS DV - TEas should be cloned on test creation

h3. Requirements * When a test is created it should clone the TEas * Cloned TEas should hold onto the original {{teaId}} * This should occur with analyzer templates and tests End State: !image-20240605-113438.png|width=1172,height=918,alt="image-20240605-113438.png"!

TST DV - Library Org TEas

TST DV - Library Org TEas

h3. Requirements * We want to separate the TEas in the tests from Library TEas. Come up with some logic that there can be library TEas that show up in the Analyte Library and TEa selection * We don’t want TEas from individual tests to show up in the TEa library

TSTS DV QNT - On test edit, TEas selected from Library should be cloned

TSTS DV QNT - On test edit, TEas selected from Library should be cloned

h3. Requirements * When editing a test, TEas selected from the library should be cloned * Cloned TEas should hold onto the original {{teaId}} * This occurs on test submission [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=2273-68117&t=CLDlsvDOIOnWxeio-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=2273-68117&t=CLDlsvDOIOnWxeio-4|smart-embed]

GLBL DV - Button Component Icon Only Size Update

GLBL DV - Button Component Icon Only Size Update

{panel:bgColor=#deebff} This task precedes [https://cualia.atlassian.net/browse/CMV-257|https://cualia.atlassian.net/browse/CMV-257|smart-link] {panel} *Description* [~accountid:712020:250fdeb1-730c-4ca0-afb0-e00b173eb4c2] Updated the Figma Icon only Button Icon sizes. Changelog updated in Notion -> [UI | GLBL | Buttons|https://www.notion.so/cualia/UI-GLBL-Buttons-552a07ae09204327b86c8ec6013c59df] Figma Link → [Icon Buttons|https://www.figma.com/design/YIk4VcC3GZlFjicwu5aBbc/Cualia-Design-System?node-id=118-8577&t=wcn7W0kpJs6pUJS1-4] *Actions* Size of the icon in Buttons in Icon Only state for sizes: base, L and XL sizes changed to 20, 24, and 28px *Second Order Effects* The original Icon size was 16px. Give the app a look see if anything looks really off * Check which components use the same icon button component. This was already explored on Figma. ** *Note* - In figma there is a difference between [Icon Button|https://www.figma.com/design/YIk4VcC3GZlFjicwu5aBbc/Cualia-Design-System?node-id=76-15825&t=3ZmPfZIbWQsmcyZl-4] and [Icon Only Button|https://www.figma.com/design/YIk4VcC3GZlFjicwu5aBbc/Cualia-Design-System?node-id=118-8589&t=3ZmPfZIbWQsmcyZl-4] *** Icon Only Button has the border around it * From [~accountid:712020:250fdeb1-730c-4ca0-afb0-e00b173eb4c2] Looked through for second order effects. There were a few such as the Reports text editor and Image upload, but in general they look fine

[Global UI] HTML Page Titles

[Global UI] HTML Page Titles

In our app all the HTML page names are just "[http://Cualia.io|http://Cualia.io|smart-link] " and I want them a bit more specific. h2. All Routes → [UIX | Routes RFR|https://www.notion.so/cualia/UIX-Routes-RFR-fb850f54a5d94534949163e0390dfb40] h2. Requirements # Pre-fetched headers are not required, page name change can be done {{onMount}} because we don't have to worry about SEO # All must use LL translations # No need to think of a clever everything in one place functional solution, just in {{+page.svelte}} is fine # We don’t need to worry about SEO.

MV-EXPTrueness QL | "Add Row" text in Qual should not be missing in Qual Trueness

MV-EXPTrueness QL | "Add Row" text in Qual should not be missing in Qual Trueness

Environment: Dev Test Condition: User is in [https://dev.cualia.io/org/Tl2p0u9W/mv/kjjpgokt1i/tests/qto8d9gdn6/qual/trueness|https://dev.cualia.io/org/Tl2p0u9W/mv/kjjpgokt1i/tests/qto8d9gdn6/qual/trueness] User is Owner Steps to replicate: # In MV, go to: Qual - Triiodothyronine Truness Result: Add Row text is missing. Only displayed is the Add icon Screen recording: [https://jam.dev/c/07976d5f-d472-4ae3-ad4b-a830c4325fcb|https://jam.dev/c/07976d5f-d472-4ae3-ad4b-a830c4325fcb|smart-link] Screenshot: !image-20240729-065950.png|width=853,height=465,alt="image-20240729-065950.png"!

PRMS BG | Under Invite Members pop up, Role dropdown should be closed upon selecting a role from the dropdown button

PRMS BG | Under Invite Members pop up, Role dropdown should be closed upon selecting a role from the dropdown button

Test Condition: # User is Owner # User is subscribed in Org Plan # User is in Team Memberships page > Invite Members pop up Environment: Dev Steps to Replicate: # In Invite Members popup, select Role dropdown button # Select any data from the dropdown button Result: # Role dropdown button did not close upon selecting a data on the dropdown button # The Role dropdown button overlaps on the other data # There’s no way to close the Role dropdown button Screen recording: [^screencast-dev.cualia.io-2024.06.18-13_12_18.webm]

Open icon in the Analyte Tests should go to the test details in a New tab

Open icon in the Analyte Tests should go to the test details in a New tab

Open icon in the Analyte Tests should go dorectly to the test details in a New tab Library --> Analyte line item --> Tests line item (click on Open icon) [https://www.loom.com/share/34883ab33824481c8e593a28474addfa?sid=fb618940-2e89-48f8-9aa8-52612f799283|https://www.loom.com/share/34883ab33824481c8e593a28474addfa?sid=fb618940-2e89-48f8-9aa8-52612f799283|smart-link] !Screenshot 2024-05-18 at 6.06.20 PM.png|width=1078,height=918,alt="Screenshot 2024-05-18 at 6.06.20 PM.png"! --> Should go directly to the Test Details in a New Tab [https://staging.cualia.io/org/Tl2p0u9W/analyzer/rtde2gpevdj/tests/quant?testId=uuav1oo7voj|https://staging.cualia.io/org/Tl2p0u9W/analyzer/rtde2gpevdj/tests/quant?testId=uuav1oo7voj] !Screenshot 2024-05-18 at 6.09.57 PM.png|width=1557,height=979,alt="Screenshot 2024-05-18 at 6.09.57 PM.png"!

ANZ TSTS QNT QL ADT | Search query also pulls from the ‘Other Names’ in the Add Test modal

ANZ TSTS QNT QL ADT | Search query also pulls from the ‘Other Names’ in the Add Test modal

When a user does a search, the search query should also pull from the ‘Other Names’ in the Add Test modal. !Screenshot_2.png|width=884,height=803,alt="Screenshot_2.png"!

[Add Qualitative Test] Add Qualitative Test button looks like disabled but it's clickable

[Add Qualitative Test] Add Qualitative Test button looks like disabled but it's clickable

*Environment*: Dev *Account*: Free plan *Test condition*: User is Analyzers page *Steps to Replicate*: # Click an analyzer # Click Qualitative Tests tab # In Qualitative Tests tab, click Add a Test button # Select any Analyte name (e.g. Lactate) # Click Continue button # In Add Qualitative Test page, check Add Qualitative Test button *Test Data used*: Email: [bianca+02@cualia.io|mailto:bianca+02@cualia.io] Password: $$testtest1 !Screen Recording 2024-05-24 at 12.01.42 PM.mov|width=1904,height=1034,alt="Screen Recording 2024-05-24 at 12.01.42 PM.mov"!

MV-Exp - Floating Save Button

MV-Exp - Floating Save Button

Create a floating save button in experiments to replace the current save methodology. The current issue is that the small save button doesn't scale to give the sense that it also saves the Summary. Thus heavily affecting User Experience. h2. *Actions* * *Save Button* → Saves ALL the test’s experiment data. This includes data in the table and experiment summary * *Reset Button* -> Resets the experiment data to its last saved state (resets the table state as well) * Deprecate the save button on the experiment table action bars ** Note that we still want the save button on the Materials table action bar to persist {panel:bgColor=#deebff} The undo redo reset buttons in the table actions bars will remain local to the tables. *However* the reset button on the floating save will reset those states. {panel}

MV-EXP QNT - TEa Visibility for MC, Prec, and Trueness

MV-EXP QNT - TEa Visibility for MC, Prec, and Trueness

The purpose of this ticket is to properly display the TEa, REa, and SEa values in these areas: # Results (Prec, MC and Trueness) # Action Bar (Prec and MC) !image-20240605-053202.png|width=30.434782608695656%,alt="image-20240605-053202.png"! !image-20240605-053232.png|width=30.434782608695656%,alt="image-20240605-053232.png"! # Test Details !image-20240605-053312.png|width=30.434782608695656%,alt="image-20240605-053312.png"! !image-20240605-053343.png|width=30.434782608695656%,alt="image-20240605-053343.png"!

ORGS BG | Organization Form contact field in settings/org/details/edit should be optional

ORGS BG | Organization Form contact field in settings/org/details/edit should be optional

Error message "contact cannot be null" displayed in Contact text box even if the text box is Optional *Environment*: Dev *Account plan:* Free *Test Condition:* User is in Account Settings page *Steps to Replicate*: # In Account settings page, click Organization menu # Click Edit button # Update the Organization Name. (e.g. Add "update" on the organization name" # Click Save button [https://www.loom.com/share/cba6753c0a8c40a9b4fa5df1bc9f2743?sid=c60847e0-b448-444c-87bb-1a446314fde6|https://www.loom.com/share/cba6753c0a8c40a9b4fa5df1bc9f2743?sid=c60847e0-b448-444c-87bb-1a446314fde6|smart-link]

TST DV QNT - Library TEas on Tests Include only Public and Org Lib TEas

TST DV QNT - Library TEas on Tests Include only Public and Org Lib TEas

h3. UI Update * Icon for public TEas * Icon for Org Lib TEas !image-20240605-051830.png|width=1243,height=1280,alt="image-20240605-051830.png"! h3. Quant Test TEa from Library filters for * Public TEas * TEas in the org library

QNT MV BG | In the Precision page, Percent Sign (%) Splits Onto a New Line When Webpage Width is Less Than 1294px

QNT MV BG | In the Precision page, Percent Sign (%) Splits Onto a New Line When Webpage Width is Less Than 1294px

Test Condition: User is using a smaller screen (Macbook), Sample should have a data Steps to replicate: # In the Quantitative Precision page, scroll down to the Sample Results # The percent sign (%) splits onto a new line when the webpage width is less than 1294px, causing layout and readability issues. [^screencast-dev.cualia.io-2024.05.31-17_12_53.webm]

MV ADT | Highlighting is off when samples are selected

MV ADT | Highlighting is off when samples are selected

Highlighting should be off when samples are selected. !Screenshot_9.png|width=1250,height=662,alt="Screenshot_9.png"!

TST - TEas added can be added to the TEa library

TST - TEas added can be added to the TEa library

h3. Goal TEas created from the test add/edit form will now have the ability to add to the library. h3. Outer Padding Changed to 32px !image-20240605-043627.png|width=1152,height=370,alt="image-20240605-043627.png"! Outer Padding Changed to 32px h3. Users can add a TEa to the Library. !image-20240605-043705.png|width=1202,height=970,alt="image-20240605-043705.png"! Add to TEa Library Checkbox * Disabled if the user doesn’t have Edit Library Permissions ** Tooltip -> Library edit permission is required to add to the library * If selected the TEa will be added to org library during submit ** Tooltip -> Tests with this analyte will have this TEa available ** The tea will be submitted on TEST form submission both for MV and Analyzer Tests

[Library Methodologies] Add/Edit Methodology

[Library Methodologies] Add/Edit Methodology

* Add URL -> org/{orgId}/library/methodology/{methodologyId}/new !Screenshot 2024-04-02 at 12.28.29 PM.png|width=80.71895424836602%,alt="Screenshot 2024-04-02 at 12.28.29 PM.png"! * Edit URL -> org/{orgId}/library/methodology/{methodologyId}/edit !Screenshot 2024-04-02 at 12.22.06 PM.png|width=80.71895424836602%,alt="Screenshot 2024-04-02 at 12.22.06 PM.png"! * User should be redirected to view methodology if not authorized to edit Library Items

PRMS DEPS - Department Permissions add/edit/delete

PRMS DEPS - Department Permissions add/edit/delete

This ticket will be handling department related permissions to add edit and create. Owners and Admins: # View # Create # Edit # Delete Members: # View # Edit As for Subscriptions: # Only the Core Users have Department Scoped Permission Roles # Free tier only have 1 Department. !Screenshot 2024-05-24 at 5.20.40 PM.png|width=1355,height=819,alt="Screenshot 2024-05-24 at 5.20.40 PM.png"!

MV-EXPPrec QL BG | Sample section should be aligned with the other section/table

MV-EXPPrec QL BG | Sample section should be aligned with the other section/table

Test Condition: User is in Qualitative Tests & Experiments Link: [https://dev.cualia.io/org/Tl2p0u9W/mv/qoqlabz88c/tests/owi24b7z0ph/qual/precision|https://dev.cualia.io/org/Tl2p0u9W/mv/qoqlabz88c/tests/owi24b7z0ph/qual/precision] User: Admin Note: Sample section is not aligned along with the other sections/table !image-20240618-085900.png|width=841,height=474,alt="image-20240618-085900.png"!

[List Analytes View] Empty Sample Types and/or Methodologies tabs should be removed

[List Analytes View] Empty Sample Types and/or Methodologies tabs should be removed

Library Sample Types and/or Methodologies tabs - if empty, these should be removed. !Screenshot 2024-05-18 at 6.24.03 PM.png|width=1462,height=894,alt="Screenshot 2024-05-18 at 6.24.03 PM.png"!

MV-EXPPrec BG QL ADT | The Agreement tooltip says “Percent of results that meet the set agreement of the reference value.”

MV-EXPPrec BG QL ADT | The Agreement tooltip says “Percent of results that meet the set agreement of the reference value.”

The Agreement tooltip says “Percent of results that meet the set agreement of the reference value.” Appears in both CV mode and TEa mode. !Screenshot_6.png|width=1717,height=452,alt="Screenshot_6.png"!

LBR TSTS | Analyte sorting lazy loading refresh issues

LBR TSTS | Analyte sorting lazy loading refresh issues

Steps to Reproduce: # Open the Analytes tab in the Library page. # Scroll down to load a subset of the analytes. # Click on any column header (e.g., "Tests") to sort the items. # Observe that only the visible items are sorted, while the rest remain unaffected. See video: [https://www.loom.com/share/05c2e1d1b1104f99a901b4d26de25fec?sid=8c0d41f3-ee2b-40a5-93f6-d99a2b477d03|https://www.loom.com/share/05c2e1d1b1104f99a901b4d26de25fec?sid=8c0d41f3-ee2b-40a5-93f6-d99a2b477d03|smart-link]

GLBL DV | UI Chip is unique and there cannot be duplicates

GLBL DV | UI Chip is unique and there cannot be duplicates

Please add a validation that each chip should be unique and there shouldn’t be any duplicates. !334663469-aa5b8945-6b71-42d6-8928-c2385233d6e2.mov|width=1292,height=638,alt="334663469-aa5b8945-6b71-42d6-8928-c2385233d6e2.mov"!

[Library Methodologies] Methodology Details

[Library Methodologies] Methodology Details

URL -> org/{orgId}/library/methodology/{methodologyId} !Screenshot 2024-04-02 at 12.13.04 PM.png|width=721,height=804,alt="Screenshot 2024-04-02 at 12.13.04 PM.png"!

MV BG | Error message is not displayed when the Manufacturer URL is valid

MV BG | Error message is not displayed when the Manufacturer URL is valid

*Environment*: Dev *Account plan*: Free *Steps to Replicate*: # In Verification Details, click Edit button # Update File Name data. E.g. (Test edit file name) # Click Save button # Error message "This is not a valid URL" is displayed for valid URL under Website URL *Expected Result*: No error message should be displayed if the data in Website URL is valid *Actual Result*: Error message was displayed in Website URL even if the entered URL is valid *Dev Note*: Removing the dashes and the period before the html will make the URL valid !image-20240527-230244.png|width=1654,height=973,alt="image-20240527-230244.png"! !Screen Recording 2024-05-20 at 6.02.38 PM.mov|width=2860,height=1654,alt="Screen Recording 2024-05-20 at 6.02.38 PM.mov"!

LBS BG | In Edit Lab, Delete Lab button and Side Menu should not move upon refresh

LBS BG | In Edit Lab, Delete Lab button and Side Menu should not move upon refresh

Environment: Dev User: Admin, Owner, Member Browser: Chrome, Safari, Firefox Test Condition: User is in Edit Lab Steps to Replicate: # In Edit Lab page, click refresh button of the browser Result: While refreshing, the Delete Lab button and Side Menu are moving [https://nimb.ws/SYPZ3Uh|https://nimb.ws/SYPZ3Uh|smart-link] !Screen Recording 2024-07-05 at 2.18.02 PM.mov|width=1914,height=1070,alt="Screen Recording 2024-07-05 at 2.18.02 PM.mov"!

LBR BG | User should be able to successfully update the Methodology Name

LBR BG | User should be able to successfully update the Methodology Name

Environment: Development Test Condition: User is in Library > Methodologies tab Steps to Replicate: # In Methodologies tab, select any Methodology # Click Edit button # In Methodology Name, update the data (e.g. Add “edit) # Click Edit Methodology button

PRMS BG | Under Invite Members pop up, option under Role dropdown should not overlap on the other fields

PRMS BG | Under Invite Members pop up, option under Role dropdown should not overlap on the other fields

Test Condition: # User is Owner # User is subscribed in Org Plan # User is in Team Memberships page > Invite Members pop up Environment: Staging and Dev Steps to Replicate: # In Invite Members popup, select Role dropdown button Result: # Options under Role dropdown button overlaps on the other fields # Options doesn’t have a background Screen recording: [^screencast-dev.cualia.io-2024.06.26-17_16_48.webm]

MV-EXPRefInt BG QNT ADT | The order of the tabs in the Reference Interval Experiment will depend on the order of items in Ref Ints dropdown

MV-EXPRefInt BG QNT ADT | The order of the tabs in the Reference Interval Experiment will depend on the order of items in Ref Ints dropdown

The order of the tabs in the Reference Interval Experiment should follow the order of items in Ref Ints dropdown. !Screenshot_19.png|width=848,height=281,alt="Screenshot_19.png"!

Free Users are not able to add the 4th test per verification

Free Users are not able to add the 4th test per verification

Free Users will not be able to add a 4th test per verification. On creation of the MV, they will only have 3 tests activated. They will not be permitted to have more than 3 activated. There will be Subscription CTA(just like the one from Organizations page [https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|smart-link] ) That says, “Looking to make changes? You’re currently on the {plan name} Plan. Your team can upgrade for more features. Would you like to upgrade now?” [https://staging.cualia.io/org/Tl2p0u9W/analyzer/rtde2gpevdj/tests/qual|https://staging.cualia.io/org/Tl2p0u9W/analyzer/rtde2gpevdj/tests/qual]

MV-EXPLoQ QNT - Statistics in should be in 2 column view

MV-EXPLoQ QNT - Statistics in should be in 2 column view

*Note* - There’s no figma design for this The statistics section in LoQ should match this 2 column format: ||*Statistics*|| || |LoQ Error Allowance|Overall Mean| |Bias|Standard Deviation| | |Total Error| !20240602-130244 - Microsoft Edge - Cualia.png|width=802,height=1006,alt="20240602-130244 - Microsoft Edge - Cualia.png"!

MV-EXPMC BG QNT ADT | Acceptable Min Samples values are between 3 and 100

MV-EXPMC BG QNT ADT | Acceptable Min Samples values are between 3 and 100

When a user puts in a valid value between 3 and 100, the system still throws an error. !Screenshot_16.png|width=1232,height=1166,alt="Screenshot_16.png"!

Delete Verifications

Delete Verifications

* To delete a verification the user has to press edit, user can delete with the button. * Flow ** Go into Verification details -> Click on Edit -> Click on Delete -> Delete Confirmation modal -> Write the name of Verification in input -> Confirm !Screenshot 2024-03-21 at 9.26.14 AM.png|width=927,height=887!

❗️BG MV-EXPPRec QL - Result Label and Sample Result

❗️BG MV-EXPPRec QL - Result Label and Sample Result

How to replicate: # Select a test [https://staging.cualia.io/org/Tl2p0u9W/mv/d93ko1g8nwr/tests/2jupe38mjam/qual/precision|https://staging.cualia.io/org/Tl2p0u9W/mv/d93ko1g8nwr/tests/2jupe38mjam/qual/precision] # Select Precision test under Select Experiment # Scroll down at the bottom to Result. # Hover over tooltip. # It is showing: !CleanShot 2024-03-15 at 12.12.26 (db808d78-7d26-4442-aa66-0936b7cb7171).png|width=546,height=199! # Also, Result is failed and therefore bottom section should be Red instead of Green. ---- The samples are also incorrect and each sample needs to prove to be within precision requirements to pass. All samples need to have passed for the experiment to also pass. The Samples in the sticky result should actually be {Samples Passed}/{Samples Total With Results}

Free Tier Users will not be able to add 2nd analyzer

Free Tier Users will not be able to add 2nd analyzer

When a free tier user tries to add new analyzers, they will not be able to and will be redirected to the subscription page. Place tooltip on left. !image-20240305-033618.png|width=100%! Assumptions: * User Type: Free * User already has 1 analyzer Steps: # User logs in to app # User navigates to Analyzers # New Analyzer Button will be disabled # User hovers over New Analyzer button and will see a tooltip that says: “You’ve exceeded the maximum number of analyzers. Would you like to upgrade?”

GLBL DV | UI Chip Inputs when in a Read Only or Disabled state should not change color on hover

GLBL DV | UI Chip Inputs when in a Read Only or Disabled state should not change color on hover

!CleanShot 2024-03-30 at 11.08.31-20240330-030844.gif|width=1016,height=709,alt="CleanShot 2024-03-30 at 11.08.31-20240330-030844.gif"! Current Behavior * Mouse hover changes color when chip is in a readonly or disabled state Expected * No mouse hover changes when chip is in a readonly or disabled state Make sure Chips behave appropriately in all other pages.

As a User, I should see the Dashboard upon logging in, so that I can view relevant data

As a User, I should see the Dashboard upon logging in, so that I can view relevant data

[https://discord.com/channels/965551040890028062/1219085471557353652/1238323898223820890|https://discord.com/channels/965551040890028062/1219085471557353652/1238323898223820890|smart-link] Upon logging in, the user will see the dashboard. Note: No roles/permissions on the UI yet. That will come after launch.

Test Experiment Summary Changes

Test Experiment Summary Changes

ORGS ADT | Active Sidebar Main Sections need to be highlighted

ORGS ADT | Active Sidebar Main Sections need to be highlighted

The current or active sidebar section should be highlighted so the user knows which section they are in. For main pages, it does highlight the sidebar section. !Screenshot 2024-05-24 at 5.31.21 PM.png|width=1410,height=805,alt="Screenshot 2024-05-24 at 5.31.21 PM.png"! For the sub page, it does not. !Screenshot 2024-05-24 at 5.31.45 PM.png|width=717,height=360,alt="Screenshot 2024-05-24 at 5.31.45 PM.png"! [~accountid:712020:250fdeb1-730c-4ca0-afb0-e00b173eb4c2] Notes The {{Selected}} state color can be found in the [https://www.figma.com/design/YIk4VcC3GZlFjicwu5aBbc/Cualia-Design-System?node-id=50-4456&t=1NtREg3XYFXENEQ0-4|https://www.figma.com/design/YIk4VcC3GZlFjicwu5aBbc/Cualia-Design-System?node-id=50-4456&t=1NtREg3XYFXENEQ0-4|smart-link] component. c_dark_palette/accent

Free Users are not able to add the 4th team member

Free Users are not able to add the 4th team member

[https://staging.cualia.io/org/Tl2p0u9W/settings/team/memberships|https://staging.cualia.io/org/Tl2p0u9W/settings/team/memberships] For For Free tier users with 3 team members but are trying to add a 4th team member, will we still retain this message here: “Your current plan only allows 3 members. Please remove members or invited accounts.” !Screenshot 2024-05-07 at 12.04.00 PM.png|width=621,height=160,alt="Screenshot 2024-05-07 at 12.04.00 PM.png"! Maintain max width of 250px.

PRMS RLS | As a Member, I am unable to create, edit, and delete Analyzers by default

PRMS RLS | As a Member, I am unable to create, edit, and delete Analyzers by default

This is to limit the capabilities of a member to Create, Edit, and Delete analyzers. Users can do these only if they are assigned to a role within that department that permits creating, editing, and/or deleting analyzers.

LBR BG | Delete button and side menu bar should not move upon clicking refresh

LBR BG | Delete button and side menu bar should not move upon clicking refresh

Environment: Development Test condition: User is in Free Plan, User is in Edit Analyte Details page Steps to Replicate: # In Edit Analyte Details page, click refresh button on the browser Screen recording: [https://nimb.ws/Xhma6li|https://nimb.ws/Xhma6li|smart-link]

TSTS QNT BG ADT | “Add one” link in Total Allowable Error modal is centered

TSTS QNT BG ADT | “Add one” link in Total Allowable Error modal is centered

The ‘Add one’ link in the Total Allowable Error Modal should be centered. *Steps to Replicate:* # Go to an Analyzer. # Go to Quantitative Tests tab. # Click on Add a Test. # Select D-Dimer. # Scroll down to Total Allowable Error. # Edit one of the fields. # See the popup. Add one link should be in the center. !Screenshot_1.png|width=1337,height=1095,alt="Screenshot_1.png"!

Team Settings | Invite Members Modal - 'Departments' radio button should be changed to 'All'

Team Settings | Invite Members Modal - 'Departments' radio button should be changed to 'All'

Steps: # Navigate to Team Settings. # Click on Invite Members. # On the Invite Members Modal, Under Description, the top selection is ‘Departments’ - this should be changed to ‘All’. !Screenshot 2024-05-24 at 5.05.07 PM.png|width=1333,height=784,alt="Screenshot 2024-05-24 at 5.05.07 PM.png"!

[Settings | My Profile] Action Buttons are in the incorrect state

[Settings | My Profile] Action Buttons are in the incorrect state

[https://bianca-cualia-io.nimbusweb.me/share/10811247/q72hbai9p0xgzrky7io5|https://bianca-cualia-io.nimbusweb.me/share/10811247/q72hbai9p0xgzrky7io5|smart-link] Steps to replicate: # Login to app # Navigate to Profile Icon, then Settings. # Click on Edit Profile. # My Profile modal pops up.

[QAL | QNT] Hovering over inactive tests should not have a mouse over state

[QAL | QNT] Hovering over inactive tests should not have a mouse over state

When hovering over inactive tests, there is a mouse over state in the shape of a hand. This should only be a cursor, no difference in hover state should be seen in inactive line items. [https://www.loom.com/share/1728d7067a6b4b8d95ad689c3720a67e?sid=e082d303-22a1-4dcb-a841-656964a457b0|https://www.loom.com/share/1728d7067a6b4b8d95ad689c3720a67e?sid=e082d303-22a1-4dcb-a841-656964a457b0|smart-link] !Screenshot 2024-05-25 190223.png|width=1248,height=500,alt="Screenshot 2024-05-25 190223.png"!

[Edit Analyte] Old Analyte should not be in the list after saving edits

[Edit Analyte] Old Analyte should not be in the list after saving edits

When editing an Analyte, the Old version should not be in the list anymore. Test should also be in the new version. # Old Version for reference. !Screenshot 2024-05-18 at 6.15.50 PM.png|width=1436,height=879,alt="Screenshot 2024-05-18 at 6.15.50 PM.png"! # Edit the Analyte. !Screenshot 2024-05-18 at 6.16.34 PM.png|width=1402,height=980,alt="Screenshot 2024-05-18 at 6.16.34 PM.png"! # Save your edits. !Screenshot 2024-05-18 at 6.16.48 PM.png|width=1409,height=948,alt="Screenshot 2024-05-18 at 6.16.48 PM.png"! # Old Version is still there. We need to remove this and get all the tests on the newer version. !Screenshot 2024-05-18 at 6.17.42 PM.png|width=1487,height=867,alt="Screenshot 2024-05-18 at 6.17.42 PM.png"!

Free Users will not be able to edit a report

Free Users will not be able to edit a report

Free Users will not be able to edit a report. There will be no difference if they hover over sections. There will be Subscription CTA(just like the one from Organizations page [https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|smart-link] ) That says, “Looking to make changes? You’re currently on the Free Plan. Your team can upgrade to the Core Plan tier to modify this report. Would you like to upgrade now?” !Screenshot 2024-05-06 at 10.32.17 AM.png|width=745,height=195,alt="Screenshot 2024-05-06 at 10.32.17 AM.png"!

Dashboard Verifications Stats

Dashboard Verifications Stats

!Screenshot 2024-03-20 at 11.03.40 AM.png|width=203,height=552! This section will have the following data: * Awaiting Approval * Tests Approved * Experiments Approved * Recently Updated (show latest 3 items, then “View More” at the bottom) Will go to the Verifications page

ORGS BG | Username should not overlap within Expanded Main Navbar

ORGS BG | Username should not overlap within Expanded Main Navbar

*Test Step:* # In log in page, enter the valid email address in Email text box: [qa+member@cualia.io|mailto:qa+member@cualia.io] # In Password, input the valid password # Click Login button *Expected Result*: Username should not overlap on the Menu section *Actual Result:* Username overlaps on the Menu section

PRMS RLS | As an Owner and Admin, I can delete MVs

PRMS RLS | As an Owner and Admin, I can delete MVs

The purpose of this ticket is to enable owners and admins to delete MVs. Currently, there is not way for an Owner to delete an MV. !image-20240605-064833.png|width=827,height=437,alt="image-20240605-064833.png"! A member can only delete an MV within a specific department of an organization if assigned to a role that allows Deleting MV. Update: We will move the "Go to Analyzers Values" button on MV Details Edit page to the the Analyzers section header below. !an.png|width=709,height=767,alt="an.png"!

MV-STG BG QL QNT ADT | The number of Experiments Selected updates accordingly when selection changes

MV-STG BG QL QNT ADT | The number of Experiments Selected updates accordingly when selection changes

When changing the number of selected(toggled) experiments from the drop down, the actual number is delayed in displaying the correct number. *Steps to replicate:* # Go to Verifications. # Pick a Verification. # Go to Experiments tab. # Unselect one of the Tests. # The number *X* in “*X* of Y tests selected” should refresh immediately. !image-20240525-102438.png|width=1562,height=508,alt="image-20240525-102438.png"! [https://www.loom.com/share/23a754dba98243dc8daa26d629ced2d2?sid=4aee5a1d-1579-4e1c-8738-111cafaafd87|https://www.loom.com/share/23a754dba98243dc8daa26d629ced2d2?sid=4aee5a1d-1579-4e1c-8738-111cafaafd87|smart-link]

ORGS - Dashboard Sidebar Text Truncated

ORGS - Dashboard Sidebar Text Truncated

*Actions* * Set the sidebar text boxes to truncate long text !20240529-162503 - Microsoft Edge - Cualia.png|width=1893,height=732,alt="20240529-162503 - Microsoft Edge - Cualia.png"!

MV-EXPLin BG QNT CLC ADT | R-Squared value in sticky results should be yellow when run results doesn't match the total required results

MV-EXPLin BG QNT CLC ADT | R-Squared value in sticky results should be yellow when run results doesn't match the total required results

R-Squared value in sticky results should be yellow when run results doesn't match the total required replicates. Total Required Results = Levels * Results Per Level. In the screenshot attached Levels = 3 Results Per Level = 5 Total Required Results = 15 The R2 value should be yellow since the table only has 9 replicates populated. !Screenshot_18.png|width=1595,height=1145,alt="Screenshot_18.png"! Check this link for the calculation source of truth. [https://docs.google.com/spreadsheets/d/1qALC5JZ3bNOKWnE9tZIj3RLEUIufXQTxwiXYOGGQGos/edit?pli=1#gid=1455221825|https://docs.google.com/spreadsheets/d/1qALC5JZ3bNOKWnE9tZIj3RLEUIufXQTxwiXYOGGQGos/edit?pli=1#gid=1455221825]

LBR BG | Data under Source dropdown button of Percent and Units should be displayed correctly

LBR BG | Data under Source dropdown button of Percent and Units should be displayed correctly

Test Environment: Dev Test Condition:n User is Owner Steps to Replicate: # In Analytes, click Add TEa button # Click Source dropdown button under Percent tab # Click Units tab # Click Source dropdown button under Units tab Result: Data of Source dropdown under Percent and Units tab are not displayed correctly. Unable to read the whole data [^screencast-dev.cualia.io-2024.07.05-12_29_02.webm]

PRMS RLS | As a Member, I am unable to create, edit, and delete MVs by default

PRMS RLS | As a Member, I am unable to create, edit, and delete MVs by default

This is to limit the capabilities of a member to Create, Edit, and Delete MVs. Users can only do these if they are assigned to a role within that department that permits creating, editing, and/or deleting MVs.

MV-EXPPrec BG QL ADT | The results at the bottom of the Verification says “Results”

MV-EXPPrec BG QL ADT | The results at the bottom of the Verification says “Results”

The results at the bottom of the Verification says “Results” !Screenshot_7.png|width=1336,height=281,alt="Screenshot_7.png"!

ORGS RLS | Implement Single Organization Restriction for Free Tier Users

ORGS RLS | Implement Single Organization Restriction for Free Tier Users

h2. *Objective* To enforce a restriction that prevents users from owning more than one organization under the free plan. This measure is aimed at preventing users from creating countless free organizations, which can lead to system abuse and resource constraints. h2. *Requirement* When a user who already owns a free plan organization attempts to create another one, the "+ New Organization" button should be disabled. !image-20240620-031025.png|width=1330,height=669,alt="image-20240620-031025.png"! h2. *Implementation Details* * *UI Change -* The "+ New Organization" button should be disabled for users who are already owners of a free tier organization. * *Tooltip Addition -* When the "+ New Organization" button is disabled, a tooltip should appear stating, {{You can only be the owner of 1 free tier organization}}. * *Backend Logic -* Implement backend validation to check the number of free plan organizations a user owns before allowing the creation of a new organization. This check should occur when the user session begins and the "+ New Organization" interface is rendered. *User Flow:* # User logs into the app. # System checks how many free plan organizations the user owns. # If the user owns 1 free plan organization: #* The "+ New Organization" button is disabled. #* The tooltip {{You can only be the owner of 1 free tier organization}} is displayed when hovering over the disabled button. # If the user does not own a free plan organization, the button remains enabled and functional.

Free Users will not be able to add 2nd department

Free Users will not be able to add 2nd department

The Add Department button will be grayed out for Free Tier Users. Subscription CTA(just like the one from Organizations page [https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|https://www.figma.com/file/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?type=design&node-id=8576-26734&mode=design&t=YE1FMuB2Axp9cj2H-4|smart-link] ) * Only on free tier * Upgrade button goes to subscription page * onClick -> Close icon ** Closes the modal with vertical up fade ** Will show back up again after 2 weeks ** Highlight moves to the header as it meets Y = 0

New Analyzer Button does not work even when there are no Analyzers on the list

New Analyzer Button does not work even when there are no Analyzers on the list

New Analyzer Button does not work even when there are no Analyzers on the list. Free tier should be able to add 1 analyzer. All other tiers should be able to add unlimited number of analyzers. !Screenshot 2024-05-18 at 4.34.18 PM.png|width=1066,height=510,alt="Screenshot 2024-05-18 at 4.34.18 PM.png"!

MV-EXPPrec MV-EXPMc BG QNT ADT | Saving should work in Free tier organizations

MV-EXPPrec MV-EXPMc BG QNT ADT | Saving should work in Free tier organizations

When the user is putting in data for the sample table runs, date should persist after saving. When editing and saving the Reference Value, the new value should persist after refresh. !image-20240527-024736.png|width=1017,height=611,alt="image-20240527-024736.png"!

[Customize Verification Report] "Remove Branding" is displayed insted of "Remove Cualia Branding"

[Customize Verification Report] "Remove Branding" is displayed insted of "Remove Cualia Branding"

Environment: Dev Test Condition: User is in Org Plan, User is in Customize Verification Report modal !image-20240523-070239.png|width=637,height=696,alt="image-20240523-070239.png"!

[Library Methodologies] List Methodologies View

[Library Methodologies] List Methodologies View

URL -> org/{orgId}/library/methodologies !Screenshot 2024-04-02 at 11.31.44 AM.png|width=665,height=669,alt="Screenshot 2024-04-02 at 11.31.44 AM.png"!

MV-EXPPrec QL ADT | The color of the circle on Select Experiment matches the color of the result icon at the bottom

MV-EXPPrec QL ADT | The color of the circle on Select Experiment matches the color of the result icon at the bottom

The color of the circle on Select Experiment should match the color of the result icon at the bottom. !Screenshot_8.png|width=1322,height=1077,alt="Screenshot_8.png"!

MV-EXPLin BG QNT ADT | The default value in the Min. Coefficient r-squared is 0.95

MV-EXPLin BG QNT ADT | The default value in the Min. Coefficient r-squared is 0.95

The default value in the Min Coefficient r-squared should be 0.95. !Screenshot_17.png|width=883,height=1066,alt="Screenshot_17.png"!

PRMS RLS BG | As a Member who doesn't have a edit and delete permission, Edit button should be disabled in Analyzer Details page

PRMS RLS BG | As a Member who doesn't have a edit and delete permission, Edit button should be disabled in Analyzer Details page

*Environment*: Dev *Test Condition*: User is a member, User is in Analyzer Details page *Link*: [https://dev.cualia.io/org/Tl2p0u9W/analyzer/4gv5efro3a2/details|https://dev.cualia.io/org/Tl2p0u9W/analyzer/4gv5efro3a2/details] Steps to Replicate: # Click the Edit button # Update any details e.g. Name # Click Update Analyzer button Result: Edit button was enabled and it shows that the user has the permission to edit an analyzer. Note: Even after clicking Update Analyzer button, the changes will not be saved.

LBR - Analyte TEa Table Org Icons and Delete TEa

LBR - Analyte TEa Table Org Icons and Delete TEa

* Analyte TEa table shows icon of whether it is from the Cualia library or the Org Library * Org library items can be deleted from Analyte TEa library

[Sign up] Increase email text field character limit from 30 -> 256

[Sign up] Increase email text field character limit from 30 -> 256

# Go to staging.cualia.io # Click sign up # Enter [qa+automated_owner_20240410_100414@cualia.io|mailto:qa+automated_owner_20240410_100414@cualia.io] in email text field Expected: [qa+automated_owner_20240410_100414@cualia.io|mailto:qa+automated_owner_20240410_100414@cualia.io] should be entered Actual: you can only type up until qa+automated_owner_20240410_10 (30 characters) !image-20240410-091328.png|width=485,height=544,alt="image-20240410-091328.png"!

ORGS | Implement Dashboard Verifications Section

ORGS | Implement Dashboard Verifications Section

h2. *Objective* Create a Verifications section on the dashboard to provide a clear and concise overview of the current status of Method Validations (MVs), including pending approvals, approved tests and experiments, recent updates, and a visual representation of MV states. h2. *Implementation Details* # *Awaiting Approval Card:* #* Display a list of verifications currently in the "Awaiting Approval" state. #* Limit the display to a maximum of 3 verifications. #* Ensure the card provides clear information on each verification. # *Tests Approved Card:* #* Display the number of tests with the MV in the approved state. #* Ensure the count is accurate and updates in real-time. # *Experiments Approved Card:* #* Display the number of experiments with MV in the approved state. #* Ensure the count is accurate and updates in real-time. # *Recently Updated Section:* #* Display up to 3 of the MVs with the most recent updates. #* Include details of the experiments that were updated. #* Provide a “View more” link that directs users to the detailed list of MVs at {{/org/{orgId}/mvs}}. # *Chart Section:* #* Develop a graphical representation of all MVs and their current status. #* Use a pie chart to show the distribution of MVs across different states. #* If no MVs are found, display the text “No verifications found”.

GLBL BG | Add icon on the Add buttons should not be cropped

GLBL BG | Add icon on the Add buttons should not be cropped

Environment: Dev Add icon on the Add buttons are cropped !image-20240607-083257.png|width=143,height=65,alt="image-20240607-083257.png"! !image-20240607-083309.png|width=143,height=48,alt="image-20240607-083309.png"! !image-20240607-083323.png|width=144,height=49,alt="image-20240607-083323.png"! [^screencast-bpconcjcammlapcogcnnelfmaeghhagj-2024.06.07-16_29_50.webm]

MV-EXPRefInt BG | Loading bar should not load on loop and Select test and Select Experiment dropdown button should respond upon click

MV-EXPRefInt BG | Loading bar should not load on loop and Select test and Select Experiment dropdown button should respond upon click

Test Environment: Development Test Condition: User is in Tests & Experiments In Select Test, user is in Lactate Test In Experiment, user is in Reference Interval Steps to Replicate: # Under Select Test dropdown, select any test. E.g. Iron [^screencast-bpconcjcammlapcogcnnelfmaeghhagj-2024.06.10-11_02_28.webm]

PRMS RLS | As an Admin, I am able to see the billing details

PRMS RLS | As an Admin, I am able to see the billing details

This ticket is created so that the Admin is able to view the following tabs on the Billing Section: # Overview # Invoices # Payment Method # Subscription Plan !image-20240605-070051.png|width=611,height=414,alt="image-20240605-070051.png"!

TSTS BG QNT ADT | Drag and Drop Reference Intervals and Interference line items when editing Tests

TSTS BG QNT ADT | Drag and Drop Reference Intervals and Interference line items when editing Tests

The user should be able to Drag and Drop Reference Intervals and Interference line items when editing Tests. When dragging the line items here are the following issues: # It sometimes disappears # You can drag it from one section to another This will need to be done in the Test Edit page in Verifications and Analyzers. !Screenshot_14.png|width=781,height=629,alt="Screenshot_14.png"!

Update | Tests | Editing, when a new analyte is created, nameAbbrev should be populated

Update | Tests | Editing, when a new analyte is created, nameAbbrev should be populated

We are updating the app library epic -> [https://cualia.atlassian.net/browse/CMV-65|https://cualia.atlassian.net/browse/CMV-65|smart-link] When a new Analyte is added through the Add/Edit Quant/Qual test flow, the UI doesn’t ask the user for the Name Abbrev. On submit, the name abbrev should default to the first 8 whole characters of the name the user entered trimmed and spaces removed. For example “H3LLo World” → “H3LLoWor”

LBR - Add TEa button

LBR - Add TEa button

* URL -> org/{orgId}/library/analyte/{analyteId} * Opens the add TEa modal, the one from test form (skips the select from library step). It all comes together, a TEa can be added. * The member has to have Library edit permissions. !Screenshot 2024-03-15 at 3.23.44 AM.png|width=449,height=918! h3. Add Library Analyte Add/Delete TEa Design [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=12853-157276&t=wsC8O0pbGOg5Iu7r-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=12853-157276&t=wsC8O0pbGOg5Iu7r-4|smart-embed]

MV-EXPPrec QL BG | Data of Sample label dropdown should still be displayed properly even if the samples are more than 6

MV-EXPPrec QL BG | Data of Sample label dropdown should still be displayed properly even if the samples are more than 6

Test Conditions: User is in Owner User is in QL Test User is in: [https://dev.cualia.io/org/Tl2p0u9W/mv/v15ig22p2gp/tests/6nh3ppy8ko2/qual/precision|https://dev.cualia.io/org/Tl2p0u9W/mv/v15ig22p2gp/tests/6nh3ppy8ko2/qual/precision] Results per day: 7 Test data: [qa+owner@cualia.io|mailto:qa+owner@cualia.io] Steps to Replicate: # In experiment settings, input 7 under Results per day # Go to table and double click a row Result: Text “Not Detected” is not fully displayed since the results per day is more than 6 !image-20240701-075806.png|width=582,height=192,alt="image-20240701-075806.png"! [^screencast-staging.cualia.io-2024.07.01-15_50_21 (1).webm]

Verification Action Bar

Verification Action Bar

* Action bar will include ** Search - All keywords visible in the table ** Department Filter ** Status Filter !Screenshot 2024-03-20 at 12.32.55 PM.png|width=1032,height=69!

Verifications Table

Verifications Table

* It will contain the following details: ** Department and Location ** Filename and Evaluator ** Progress ** Analyzer Display Name, Identifier, and ** Manufacturer ** Status ** Last Modified Date * Column widths seen in the FSigma are the minimum widths. * When someone clicks into a verification or anywhere on the whole row, it will take them to the verification details page inside the verification !Screenshot 2024-03-20 at 12.23.27 PM.png|width=100%! * *‘No verifications’ page* If there are no verifications created, the application will prompt them to create a new verification with a button !Screenshot 2024-03-20 at 12.42.17 PM.png|width=100%!

Dashboard Organizations Section

Dashboard Organizations Section

* Add lazy loading for each API call.

General Points and Properties

General Points and Properties

* Dropdown menu -> if used the dropdown option can execute certain actions like filters or data changes * Color keys ** Hidden, Color, Sorting should be configurable ** If there are greater than 5 groups, the 5th key is other and the sum of all the other keys * Mouseover behavior of donut item ** The pie portion will expand to match the green state size *** 0.5s Slow size transition on mouseover and mouse off * Tooltip to the right !Screenshot 2024-03-20 at 10.45.45 AM.png|width=384,height=724!

Dashboard Analyzers and Tests Section

Dashboard Analyzers and Tests Section

General Points and Properties

General Points and Properties

* Color keys ** Hidden, Color, Sorting should be configurable ** If there are greater than 5 groups, the 5th key is other and the sum of all the other keys * Bar width (26px) and space between bars (40px) are min widths * If there are too many bars to fit within the X viewspace, allow horizontal scrolling of the graph ** !Screenshot 2024-03-18 at 3.53.03 PM.png|width=1303,height=815! REACH: Y axis persists on

QA | Login | Update automated-id

QA | Login | Update automated-id

The Plan !image-20240406-194300.png|width=1101,height=926,alt="image-20240406-194300.png"! Brain dump * Naming convention for data-testid - {page-element-description} - [https://www.linkedin.com/advice/1/how-do-you-name-html-classes-ids-skills-html|https://www.linkedin.com/advice/1/how-do-you-name-html-classes-ids-skills-html|smart-link] * Removal of test data on prod build - [https://www.reddit.com/r/sveltejs/comments/15fdsrj/how_to_remove_testing_data_attribute_during_build/|https://www.reddit.com/r/sveltejs/comments/15fdsrj/how_to_remove_testing_data_attribute_during_build/|smart-link] * Format sample for data-testid - [https://svelte-recipes.netlify.app/testing/|https://svelte-recipes.netlify.app/testing/|smart-link]

Architecture for MV Approvals, Update Timestamp and Updated by User

Architecture for MV Approvals, Update Timestamp and Updated by User

h1. Context Dashboard components will rely mostly on data related to timestamps of when was the last MV updated and who made the last update. There’s also a requirement for tracking MV approvals. Currently, our architecture doesn’t cater for these requirements. h1. Requirements h2. Setup table for approvals This table will be used to track the current approval progress and approval changes of an MV. This will contain the following columns * approvedByMembershipId → text | null * approvedByUserName → text * mvId → fkey to mv_s, pkey * status → mvapprovalstatus (incomplete, complete, approved) * created_at → timestamptz Currently, in our mv_s table, we have {{approvalStatus}} column, we will no longer need this. Removing this might need minor adjustments to our API calls within MV. We also need to setup the RLS for this new table, below are the requirements * Owner → Can update * Admin → Can update * Member - Can only update when assigned to a role within the department that has the {{mvApprove}} permission. Another approach is through postgres auditing extension. But we’ll *not* go with this one. It’s just for future reference. * [https://supabase.com/blog/postgres-audit|https://supabase.com/blog/postgres-audit|smart-link] * [https://github.com/supabase/supa_audit|https://github.com/supabase/supa_audit|smart-link] h2. Setup MV related entities to update MV’s {{updated_at}} column Currently, changes to MV tests, analyzer, details, reports, experiments, samples doesn’t update the MV’s {{updated_at}} column, we’ll need to find a way to update the value so that it appears correctly on the Organization dashboard. We also need to add a new column {{updatedByMembershipId}} and {{updatedByUserName}}. Below are the pages where updates occur for an MV and which tables are updated * MV Details Form → updates {{analyzers}} and {{mv_s}} table. * MV Settings Qual and Quant → updates {{tests}} index column and {{experiments}} active column * MV Settings Experim

[Edit Analyte Form] Delete Modal

[Edit Analyte Form] Delete Modal

* URL -> org/{orgId}/library/analyte/{analyteId}/edit * Cancel onClick -> closes modal * Delete onClick -> deletes analyte and redirects to library analytes !Screenshot 2024-03-15 at 3.58.59 AM.png|width=398,height=268!

[Analyte Details] Back to Analytes

[Analyte Details] Back to Analytes

* URL -> org/{orgId}/library/analyte/{analyteId} * onClick -> Returns to analytes page with same params as previous page ** See if it’s possible to pull the URL from history.back() if it’s the analytes page. This may be the a good way. !Screenshot 2024-03-15 at 3.19.18 AM.png|width=1057,height=874!

[Analyte Details] Analyte Tests Table

[Analyte Details] Analyte Tests Table

* URL -> org/{orgId}/library/analyte/{analyteId} * UI shows min width, table can stretch * All columns are sortable !Screenshot 2024-03-15 at 3.27.29 AM.png|width=46.526772793053546%! * Col 1 -> Header: “Test” ** Test Name * Col 2 -> Header: “Department” ** Sort by Department Name ** Line 1 -> Location Name ** Line 2 -> Department Name * Col 3 -> Header: “Analyzer” ** Sort by analyzer name and analyzer identifier ** Line 1 -> Analyzer Name + Identifier ** Line 2 -> “By “ Manufacturer Name * Icon Button ** onClick -> Opens analyzer test in new window No Tests * Show no test found text !Screenshot 2024-03-15 at 3.31.15 AM.png|width=937,height=251!

[Analyte Details] Upgrade for TEas CTA

[Analyte Details] Upgrade for TEas CTA

* URL -> org/{orgId}/library/analyte/{analyteId} * If the org is on the Free Plan show the upgrade CTA. * Upgrade button onClick -> takes user to billing subscriptions page * Close Button onClick -> closes the modal ** It should reappear every 2 weeks (I recommend keeping it in the membership table as a date field !Screenshot 2024-03-15 at 3.39.08 AM.png|width=695,height=381!

Dashboard Notifications Column

Dashboard Notifications Column

* 2 Views * Vertical (right side) if view width (not including sidebar) >= 1120px ** Top y position is stickied to top * Else horizontal view is shown. ** No Sticky ** No pending invitations card !Screenshot 2024-03-20 at 11.08.18 AM.png|width=281,height=884!

[Analyte Details] Edit Button

[Analyte Details] Edit Button

* URL -> org/{orgId}/library/analyte/{analyteId} * Goes to Edit Analyte page * Disabled If ** User does not have permission to edit library fields (Permission settings to be added in the future) !Screenshot 2024-03-15 at 3.21.13 AM.png|width=1058,height=909!

[Add/Edit Analyte Form] Form Items

[Add/Edit Analyte Form] Form Items

* Add URL -> org/{orgId}/library/analyte/{analyteId}/new * Edit URL -> org/{orgId}/library/analyte/{analyteId}/edit * User should be redirected to view analyte if not authorized to edit Library Items * For all form texts use the default localization ** Exception: Analyte Name -> “Full name of the analyte” !Screenshot 2024-03-15 at 3.51.58 AM.png|width=70.5522971652004%! * Analyte Name ** Required ** Max length 32 * Analyte Name Abbrev ** Required ** Max length 10 ** Analytes of test edit will have to be updated to include name abbrev -> [Ticket|https://cualia.atlassian.net/browse/CMV-68] * Other Analyte Names -> Chip input ** Not required *** Note: In the database this field is required. This is the only Postgres array we use in the DB. The DB will receive an empty array if empty ** Max length 120 ** Note: in the database this field is required. This is the only Postgres array we use in the app

[Analyte Details] Analyte TEas Table

[Analyte Details] Analyte TEas Table

* URL -> org/{orgId}/library/analyte/{analyteId} * UI shows min width, table can stretch x !Screenshot 2024-03-15 at 3.36.09 AM.png|width=565,height=187! * Todo: Add/Edit/Remove TEa -> Ticket * Col 1 -> Header: “Source” ** Line 1 -> TEa Source Name Abbrev ** Line 2 -> TEa Source Name * Col 2 -> Header: “Amount” * Col 3 -> Header: “Unite” No TEas * Show no TEas found text !Screenshot 2024-03-15 at 3.37.16 AM.png|width=564,height=158!

[Add/Edit Analyte Form] Delete Button (only for edit analyte, hidden on add)

[Add/Edit Analyte Form] Delete Button (only for edit analyte, hidden on add)

* Add URL -> org/{orgId}/library/analyte/{analyteId}/new * Edit URL -> org/{orgId}/library/analyte/{analyteId}/edit * User should be redirected to view analyte if not authorized to edit Library Items * onClick -> opens delete analyte modal * Disabled if ** Analyte is public *** Tooltip: “This analyte is part of the Cualia library and cannot be deleted” ** Analyte has tests attached to it (within organization) *** Tooltip: “All tests must be removed from the analyte before it can be deleted” !Screenshot 2024-03-15 at 3.46.58 AM.png|width=796,height=859!

[List Analytes View] Add Analyte Button

[List Analytes View] Add Analyte Button

* URL -> org/{orgId}/library/analytes * onClick -> Opens add Analyte !Screenshot 2024-03-15 at 3.02.19 AM.png|width=567,height=574! !Screenshot 2024-03-15 at 3.03.35 AM.png|width=562,height=613! * Disabled If ** User does not have permission to edit library fields (Permission settings to be added in the future -> [https://cualia.atlassian.net/browse/CMV-45|https://cualia.atlassian.net/browse/CMV-45|smart-link] )

Permissions for Library Add and Edit

Permissions for Library Add and Edit

We are updating the app library epic -> [https://cualia.atlassian.net/browse/CMV-65|https://cualia.atlassian.net/browse/CMV-65|smart-link] This section has add edit delete privileges for library items and we will need to update permissions to allow or not allow these. !image-20240313-105603.png|width=1600,height=2546! h3. Permissions Page Tasks [UIX | Settings | Team Roles: Edit Role Permissions [IN PROG] (notion.so)|https://www.notion.so/cualia/UIX-Settings-Team-Roles-Edit-Role-Permissions-IN-PROG-2cc7052395dc4624b055b8d999cfe061] * In {{org/Tl2p0u9W/settings/team/role/PxRc6T6u9skF/permissions}} for each of the permissions that are only available to admins add a tooltip “This action is only available to Admins” * Hide the billing section since it is owner only * Update the Memberships section header text to “Memberships (Admins only)” * Add section “Library - Analytes, Sample Types, Methodolgies” after Memberships ** See Library ** Edit Library Items ** Delete Library Items * Library item permissions need to be added to the Membership Roles table Permissions System ** Also include “Add Library Items” just in case. We don’t need it in the UI but we may need it in the DB in the future ** We will skip the RLS requirements for this and just implement the permission _frontend_ side {panel:bgColor=#deebff} We are specifically not including an “*Add to Library*” because it heavily affects the test edit uiux. Anyone with Analyzer Add/Edit access can add a library item. {panel}

Dashboard Nav Bar

Dashboard Nav Bar

!Screenshot 2024-03-20 at 11.22.09 AM.png|width=821,height=77! * The first nav bar tab scrolls all the way to the top * The other nav bar tab scrolls to the header