Angular purchase orders: can't edit fund after PO has been activated

Bug #1991487 reported by Jane Sandberg
58
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
High
Unassigned

Bug Description

Reported by Christine Morgan:

"In the dojo interface it is currently possible to use the batch updater in the purchase order to update the fund in selected line items after the purchase order has been activated. Our libraries use this to change the fund when they have accidentally used the wrong fund, have decided to use a different fund, or have uploaded a file with the wrong fiscal year set. In the new interface I see that the batch update option in the PO Actions menu is disabled after the purchase order has been activated so that it is now not possible to update funds. I realize that everything else in the batch updater, except possibly for the collection code, should be disabled after PO activation. The loss of the ability to update the fund, however, is an issue for us. If the batch updater could remain active after PO activation, with only the fund and possibly collection code enabled, that would be ideal but just leaving the batch update option active would give us what we have now."

Here are the steps I took to reproduce this with the concerto data set:

1) Acquisitions > Purchase Orders
2) Do a search for on-order purchase orders.
3) You should get at least one matching PO (PO #2). Click its name.
4) Try to find something in the UI that allows you to change the fund on one of the items connected to the first line item.

tags: added: regression
tags: added: acq-po
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Tiffany's comment from the original LP this came up on

"Per the AIG, we don't consider this particular regression a blocker for Sprint 4 getting into 3.10, but we *do* consider it a blocker for removing the PO/LI dojo interface(s)."

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

I've given this bug an importance of high since the AIG considers it a blocker for removing the PO/LI dojo interfaces and the new angular PO/LI interfaces have now been in for 2 versions.

Changed in evergreen:
importance: Undecided → High
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Confirmed this is still an issue in 3.11

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.