Anonymous | Login | Signup for a new account | 2021-01-22 12:05 GMT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0000383 | SiT! | billing | public | 2009-01-09 19:30 | 2011-08-06 17:00 | ||||||||
Reporter | paulh | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | feature | Reproducibility | N/A | ||||||||
Status | confirmed | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0000383: Lock 'old' services | ||||||||||||
Description | Might be useful if services could be locked so no more billable items can be charged against them. Could do this automatically as well on services with <= $0 on them when a new service is added | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
![]() |
|
Tomse (developer) 2011-08-06 14:14 |
this would be useful |
ivan (administrator) 2011-08-06 17:00 |
Yeah, locking could also prevent editing the service. And also editing/transferring the balance. Maybe rather than call it a lock, "inactive" may be better since that's the term we use for other items in SiT!. |
![]() |
|||
Date Modified | Username | Field | Change |
2009-01-09 19:30 | paulh | New Issue | |
2011-08-06 14:14 | Tomse | Note Added: 0004147 | |
2011-08-06 14:14 | Tomse | Assigned To | => Tomse |
2011-08-06 14:14 | Tomse | Status | new => confirmed |
2011-08-06 16:17 | Tomse | Assigned To | Tomse => |
2011-08-06 17:00 | ivan | Note Added: 0004169 |
Copyright © 2000 - 2021 MantisBT Team |