Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1758

Add plugin to automatically cancel services

    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

          Activity

          cody Cody Phillips (Inactive) created issue -
          cody Cody Phillips (Inactive) made changes -
          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).
          cody Cody Phillips (Inactive) made changes -
          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.
          cody Cody Phillips (Inactive) made changes -
          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.
          cody Cody Phillips (Inactive) made changes -
          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.
          Hide
          cody Cody Phillips (Inactive) added a comment -

          Depends on CORE-1759 to 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).

          Show
          cody Cody Phillips (Inactive) added a comment - Depends on CORE-1759 to 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).
          cody Cody Phillips (Inactive) made changes -
          Link This issue is blocked by CORE-1759 [ CORE-1759 ]
          cody Cody Phillips (Inactive) made changes -
          Security Private [ 10000 ]
          cody Cody Phillips (Inactive) made changes -
          Story Points 5
          cody Cody Phillips (Inactive) made changes -
          Sprint 3.6.0 Sprint 1 [ 15 ]
          cody Cody Phillips (Inactive) made changes -
          Story Points 5 3
          cody Cody Phillips (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          cody Cody Phillips (Inactive) made changes -
          Fix Version/s 3.6.0 [ 10600 ]
          cody Cody Phillips (Inactive) made changes -
          Labels test
          cody Cody Phillips (Inactive) made changes -
          Labels test
          cody Cody Phillips (Inactive) made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          cody Cody Phillips (Inactive) made changes -
          Link This issue testing discovered CORE-1795 [ CORE-1795 ]
          tyson Tyson Phillips (Inactive) made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              cody Cody Phillips (Inactive)
              Reporter:
              cody Cody Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                28/Sep/15

                Agile