Skip to content

LIMS-1786: Add Dewars column to Shipments page#958

Merged
ndg63276 merged 1 commit intopre-release/2025-R4.2from
improvement/LIMS-1786/add-dewars-column-to-shipments-page
Sep 16, 2025
Merged

LIMS-1786: Add Dewars column to Shipments page#958
ndg63276 merged 1 commit intopre-release/2025-R4.2from
improvement/LIMS-1786/add-dewars-column-to-shipments-page

Conversation

@ndg63276
Copy link
Copy Markdown
Collaborator

JIRA ticket: LIMS-1786

Summary:

Much like the /visits page has a column for dewars, we should do the same for the /shipments page.

Changes:

  • Add a dewars column
  • Merge the Outgoing and Return Contacts columns into one column, displaying both if they are different
  • Edit the column numbers that should be hidden on mobile

To test:

  • Go to a proposal, then go to /shipments
  • Check there is a Dewar(s) column, with the dewar name(s) in it
  • Check there is a single Lab Contact field
  • Edit a shipment so it has different outgoing and return lab contacts, check both are displayed on the shipments page

@ndg63276 ndg63276 changed the base branch from master to pre-release/2025-R4.2 September 16, 2025 09:58
@ndg63276 ndg63276 merged commit 19ec50f into pre-release/2025-R4.2 Sep 16, 2025
2 checks passed
@ndg63276 ndg63276 deleted the improvement/LIMS-1786/add-dewars-column-to-shipments-page branch September 16, 2025 10:00
ndg63276 added a commit that referenced this pull request Sep 30, 2025
* LIMS-1844: Update archiving messages for 'il' proposals (#977)

* LIMS-1807: Leave 'Mark Dispensing' button active until cancelled (#967)

* LIMS-1799: Checks for safety level should be case insensitive (#955)

* LIMS-1786: Add Dewars column to Shipments page (#958)

* LIMS-1426: Allow setting of pipeline when ranking samples (#950)

* LIMS-1783: Add parent container dropdown for gridboxes (#965)

* LIMS-1903: Fix display of shipping labels (#984)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants