Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.6.0-b1
-
Component/s: None
-
Labels:None
Description
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following:
- Schedule Cancellation Days After Suspended (Never, 0 Days, 1 Day, 2 Days, ... 60 Days)
- Cancel Services Days After Suspended (Never, 0 Days, 1 Day, 2 Days, ... 60 Days)
The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, the first setting must be <= to the second setting.
The plugin would ONLY SCHEDULE cancellation for services THAT ARE CURRENTLY SUSPENDED. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled.
The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly.
Issue Links
- is blocked by
-
CORE-1759 Unschedule cancellation when service is unsuspended
- Closed
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Cancel Services Days After Past Due (Never, 1 Day, 2 Days, ... 60 Days) The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days). |
Description |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days). |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Schedule Cancellation Days After Suspend (Never, 1 Day, 2 Days, ... 60 Days) - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, *the first setting must be <= to the second setting*. The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly. |
Description |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Schedule Cancellation Days After Suspend (Never, 1 Day, 2 Days, ... 60 Days) - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, *the first setting must be <= to the second setting*. The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly. |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Schedule Cancellation Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, *the first setting must be <= to the second setting*. The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly. |
Description |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Schedule Cancellation Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) - Cancel Services Days After Suspended (Never, 1 Day, 2 Days, ... 60 Days) The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, *the first setting must be <= to the second setting*. The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly. |
Someone has requested the ability to automatically cancel provisioned services after X days past due.
The plugin would ask for the following: - Schedule Cancellation Days After Suspended (Never, 0 Days, 1 Day, 2 Days, ... 60 Days) - Cancel Services Days After Suspended (Never, 0 Days, 1 Day, 2 Days, ... 60 Days) The first setting controls when a service receives a scheduled cancellation date. The actual date is calculated based on the second setting, which controls what date (based on the number of days after the service has been suspended) to set the cancellation date. For this reason, *the first setting must be <= to the second setting*. The plugin would *ONLY SCHEDULE* cancellation for services *THAT ARE CURRENTLY SUSPENDED*. This allows Blesta core to handle the cancellation via existing cron job, and ensures that clients that are not configured for auto suspension are never auto cancelled. The plugin would simply create a cron task, search for services that meet the criteria (are suspended, and have been suspended for at least the given number of days), and set their cancellation date accordingly. |
Security | Private [ 10000 ] |
Story Points | 5 |
Sprint | 3.6.0 Sprint 1 [ 15 ] |
Story Points | 5 | 3 |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 3.6.0 [ 10600 ] |
Labels | test |
Labels | test |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Link | This issue testing discovered CORE-1795 [ CORE-1795 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Depends on
CORE-1759to ensure that the scheduled cancellation is removed if the service was unsuspended it was scheduled for cancellation in advance of the actual cancellation date (i.e. "Cancel Services Days After Suspended" is > 0 Days).