Bug 14851 - Change terminology for budget being "locked" to "disabled"
Summary: Change terminology for budget being "locked" to "disabled"
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-18 14:13 UTC by Kyle M Hall
Modified: 2020-06-04 20:32 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2015-09-18 14:13:51 UTC
We've found that many librarians are confused by the term "locked" being use for budgets. It would make much more sense to use the term "disabled".
Comment 1 Katrin Fischer 2015-09-29 22:13:34 UTC
Hm, have been thinking about this, I think disabled would mean that it cannot be used anymore at all, while I think the feature is meant to only stop people from changing the funds after initial creation (like changing the amounts). From the help file:

Locking a budget means that Funds will not be able to be modified by librarians

So 'locked' seems clearer to me then 'disabled', but we should probably check how the feature is implemented.
Comment 2 Katrin Fischer 2019-09-01 21:54:57 UTC
Closing, please reopen, if you disagree. See also: bug 23524 and bug 22786 for some newer developments.