Web client: Can't create billing type (silent failure)

Bug #1777909 reported by tji@sitka.bclibraries.ca
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

3.0.1

No response when attempting to add a new billing type on the web client.

tags: added: webstaffclient
Revision history for this message
Terran McCanna (tmccanna) wrote :

We are on the 3.0.2 web client and I am able to successfully create a new billing type.

Revision history for this message
Courtney Brown (courtney.brown) wrote :

We are experiencing this issue as well when trying to delete old billing types and creating new billing types.

Revision history for this message
Cesar V (cesardv) wrote :

I tested this on the latest master and was able to freely add and delete billing types as long as I had the proper permission(s) to do so for that Org. Unit. Dojo will fail silently if the staff user is not allowed to perform a specific action - you will see a console error being logged (ex: "VM2218:297 Uncaught _CUD: Error creating, deleting or updating {"__c":"cbt","__p":["101","Misc","1",null,null,null,null]}")

tags: added: billing
removed: webstaffclient
Revision history for this message
Terran McCanna (tmccanna) wrote :

I'm leaning towards marking this Won't Fix because it appears to be a permissions issue, but I am open to opposing viewpoints.

tags: added: admin-pages circ-billing permissions
removed: billing
tags: added: silentfailure
Revision history for this message
Terran McCanna (tmccanna) wrote :

Keeping this open due to the silent failure issue.

summary: - Web client: Can't create billing type
+ Web client: Can't create billing type (silent failure)
Changed in evergreen:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Galen Charlton (gmc) wrote :

I took a quick look, and now that that particular interface is Angularized, I think the issue is fixed:

- if you don't have permission to add billing types, the create button is disabled
- if you somehow worked around that, the Angular interface will display an error toast if you attempt to save

Changed in evergreen:
status: Confirmed → Won't Fix
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.