Y24-173 - As developers we would like a separate printing component that can be used in different views to centralise printing, reduce technical debt, make it easier to maintain and that is reusable for new pages and reduces the amount of testing we need to do.

[stevieing]

User story
Y24-173 - As developers we would like a separate printing component that can be used in different views to centralise printing, educe technical debt, make it easier to maintain and that is reusable for new pages and reduces the amount of testing we need to do.

Currently we have a printer modal and a print job in many different views which are also tested separately. Moving this to a single component would make it easier to maintain. We would also be able to reuse it for new views. It would also mean we do not need to retest this functionality in every view.

Who are the primary contacts for this story
Steve

Who is the nominated tester for UAT
PSD

Acceptance criteria
To be considered successful the solution must allow:

• Removal of the printer modal
• Creation of a composable which will allow the user to select printers and print labels
• Reuse of the PrintJobType (may need refactoring) and the label types.
• A single place to test printing so that tests are removed from the views
• Removal of printing functionality for all views that are using it except label printing page and general reception.

Dependencies
This story is blocked by the following dependencies:

• #<issue_no.>
• sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

• #<issue_no.>
• sanger/#<issue_no.>

Additional context
Add any other context or screenshots about the feature request here.