web client: default billing type price does not populate when there is already a value in the amount field

Bug #1776757 reported by Kathy Lussier on 2018-06-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

In the web client, when you bill a patron, if you select a billing type with a default price, the number will not populate the Amount field it already had a value.

To replicate:

1. Create two billing types, each with a default price.
2. Go to a patron's bills tab and click to create a bill.
3. Select one of the new billing types. The Amount field will populate with the default price as expected.
4. Select the other billing type. The amount field does not change to the new default price.

My expectation is that the Amount field would populate with the default price whether or not there is a pre-existing value in that field.

Lindsay Stratton (lstratton) wrote :

Also if a billing type does not have a default amount associated, selecting it will not clear a previously selected/entered amount.

Michele Morgan (mmorgan) wrote :

Marking confirmed. In the xul client, the Amount field updates to the default_price for the selected billing type each time one is selected. If a billing type with NULL default_price is selected, the Amount box clears. The web client should behave similarly.

Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers