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

Add event: On service status change

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Duplicate
        • Affects Version/s: 3.0.0.b5
        • Fix Version/s: Short Term
        • Component/s: None
        • Labels:
          None

          Description

          Add an event to the system for service status change, ie pending, active, in-review, suspended, cancelled.

          It may be that each of these changes may need to be separate events, but I think a single event that maybe passes in the from status, and to status along with all data associated with the service would be ideal.

          See http://staging.blesta.com/forums/index.php?/topic/527-event-request-activate-service/

            Issue Links

            relates to

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1663 Add event: On service cancel

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1664 Add event: On service suspension

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1665 Add event: On service unsuspension

            • Major - Major loss of function.
            • Closed

              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              tyson Tyson Phillips (Inactive) added a comment -

              I'm going to close this as not relevant any longer. As you mentioned we now have an event for the object being updated, of which the status may also be included. We don't trigger separate events for data attributes on objects that change--that would provide a much higher level of granularity than I think is necessary, at least for now.

              Show
              tyson Tyson Phillips (Inactive) added a comment - I'm going to close this as not relevant any longer. As you mentioned we now have an event for the object being updated, of which the status may also be included. We don't trigger separate events for data attributes on objects that change--that would provide a much higher level of granularity than I think is necessary, at least for now.
              Hide
              Permalink
              jonathan Jonathan Reissmueller added a comment -

              We added a service edit event in CORE-1415. Is it necessary to specifically have a status change event or can this be closed?

              Show
              jonathan Jonathan Reissmueller added a comment - We added a service edit event in CORE-1415. Is it necessary to specifically have a status change event or can this be closed?
              Hide
              Permalink
              admin Paul Phillips added a comment -

              By all associated data, I think configurable option data is implied as well, which should be included.

              Show
              admin Paul Phillips added a comment - By all associated data, I think configurable option data is implied as well, which should be included.
              Hide
              Permalink
              admin Paul Phillips added a comment -

              This was recently requested, we should take a look at implementing this.

              Show
              admin Paul Phillips added a comment - This was recently requested, we should take a look at implementing this.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  admin Paul Phillips
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: