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

          Activity

          Hide
          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.
          Hide
          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
          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
          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.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: