Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0
-
Fix Version/s: 4.3.0-b1
-
Component/s: Staff Interface
-
Labels:None
Description
A service may be suspended in 1 of 2 ways.
1. Automatically by the system.
2. Manually by a staff member.
In the case of #1, the system only suspends services due to late payments.
In the case of #2, the staff member may manually suspend a service for any number of reasons.
The suspend email template should contain the reason.
If by the system, it should contain the text from a language file. "Non-Payment"
If by the staff member, the staff member should be able to enter a custom reason. When selecting Suspend under Actions, display a text field directly below the drop down as pictured.
Issue Links
- Testing discovered
-
CORE-2580
Services using the none module cause certain cron tasks to fail
-
- Closed
-
Activity
A list of predefined reasons would be good, but there may be cases when they want to put something personal in there.. like "I called you a million times, and now I have to suspend this." or something.
Going to push this one back, not that important.
Paul Phillips
added a comment - A list of predefined reasons would be good, but there may be cases when they want to put something personal in there.. like "I called you a million times, and now I have to suspend this." or something.
Going to push this one back, not that important. Staff entering a reason manually is fine, no need to have predefined reasons to start with.
Paul Phillips
added a comment - Staff entering a reason manually is fine, no need to have predefined reasons to start with. Is this reason intended to be saved, or only set specifically for the email that is sent?
Tyson Phillips (Inactive)
added a comment - Is this reason intended to be saved, or only set specifically for the email that is sent? The reason should be saved, and probably admins should be able to see it when managing the suspended service. I don't think we need to keep a record of all suspensions, just what the latest reason is.
Paul Phillips
added a comment - The reason should be saved, and probably admins should be able to see it when managing the suspended service. I don't think we need to keep a record of all suspensions, just what the latest reason is. 
I imagine admins would want to have a list of predefined suspension reasons, or at least be able to select the system-defined reasons, no?