web client serials: cannot bind issues

Bug #1717600 reported by Andrea Neiman
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Invalid
Medium
Unassigned

Bug Description

3.0 beta

I am having trouble getting issues bound; I have tried several combinations and they all fail. I get the "failed to save issuance" toaster but nothing in the console.

I'm not super knowledgeable about serials so I would definitely appreciate another set of eyes on this to rule out operator error.

This had been working previously in the web client.

Andrea Neiman (aneiman)
Changed in evergreen:
importance: Undecided → Medium
milestone: none → 3.0.1
Changed in evergreen:
milestone: 3.0.1 → 3.0.2
Revision history for this message
Angela Kilsdonk (akilsdonk) wrote :

I am also unable to bind issues in 3.0.1. I get the "failed to save issuance" message as well.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Dan Wells (dbw2) wrote :

I feel like I hit this in testing and got by it, though I have no record of what I might have done. It is possibly just a missing (or inadequate) bind template?

We are migrating to 3.0 in late December, and use binding weekly, so I will be able to give this some clearer attention in the next few weeks if nobody else jumps on it.

Revision history for this message
Holly Brennan (hollyfromhomer) wrote :

This is happening in 3.0.0 as well.

Revision history for this message
Andrea Neiman (aneiman) wrote :

Dan is correct -- marking this one invalid; it will be addressed in the documentation.

Changed in evergreen:
status: Confirmed → Invalid
Revision history for this message
Angela Kilsdonk (akilsdonk) wrote :

Upon further testing, I'm seeing in 3.0.1 that if you try to reuse one of the original barcodes when binding the items, the action will fail. If you replace the original barcode with a new one, the items will be bound together successfully. I'll add this to the documentation.

Andrea Neiman (aneiman)
Changed in evergreen:
milestone: 3.0.2 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.