[Koha-bugs] [Bug 27845] cash_management needs default register setting

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27845

Christopher Brannon <cbrannon at cdalibrary.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|19.11                       |master

--- Comment #6 from Christopher Brannon <cbrannon at cdalibrary.org> ---
(In reply to Martin Renvoize from comment #5)
> I don't understand the request here.. you can set the register for your
> session (and override it at the time of the transaction).
> 
> The default at branch level is indeed designed for the case where a register
> may be shared in which case logging in at that branch automatically selects
> the branch default register for the session.
> 
> Do you're staff users always sit at the same desk then?
> 
> Either way.. to improve this we need a clear specification against what
> currently happens in the latest release (as this would be an enhancement)..
> and I would not be able to commit to it without sponsorship

In answer to your request for clarification...

Our upstairs desk has a cash box.  Our downstairs desk has a cash box.  We have
to setup a register for each.  Both desks are at the SAME BRANCH.  Staff at the
downstairs desk log into Koha with one account at that desk, and the staff
upstairs log into Koha with another account at that desk.  TWO separate
accounts at TWO different desks in the SAME BRANCH.

It is currently IMPOSSIBLE to set a default for each user.  I can only set a
default per BRANCH.  This makes it necessary for staff to at one of the desks
to change the register for EVERY transaction.

I see no setting for setting the register for a session.  The POS does not
remain on whatever register you choose.  It always goes back to the default,
which is not what is wanted for BOTH desks.  If the register remaining
unchanged during a session relies on session history, then that is a problem,
because we specifically do not allow our browsers to retain history.

It is PREFERRED that if you give a patron a permission to use the Point of Sale
feature, that you could set which register at their branch is THEIR default at
that time.

Currently I work around this issue with jQuery, to see who is logged in, and
set their register.  I do not see this as a major project.  Probably a new
field in a table and a dropdown option next to the point of sale preference at
most.  I could be over simplifying it.  But, there it is.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.