Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.0-b1
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      Plugins already support events by registering themselves during install/upgrade, which gets saved to `plugin_events` with a callback that is invoked when the event is triggered.

      We need an observer for the core to support events as well. I am thinking a new `system_events` table that supports the same events as plugins, which includes the event name and the path to the file to load, or the class defined by namespace (preferably).

        Issue Links

          Activity

          tyson Tyson Phillips (Inactive) created issue -
          tyson Tyson Phillips (Inactive) made changes -
          Field Original Value New Value
          Component/s Staff Interface [ 10000 ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue blocks CORE-2698 [ CORE-2698 ]
          Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          tyson Tyson Phillips (Inactive) made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 4 hours, 6 minutes [ 14760 ]
          Worklog Id 11142 [ 11142 ]
          tyson Tyson Phillips (Inactive) made changes -
          Time Spent 4 hours, 6 minutes [ 14760 ] 1 day, 2 hours, 35 minutes [ 38100 ]
          Worklog Id 11151 [ 11151 ]
          Automated transition triggered when Tyson Phillips (Inactive) created pull request #444 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          tyson Tyson Phillips (Inactive) made changes -
          Time Spent 1 day, 2 hours, 35 minutes [ 38100 ] 1 day, 4 hours, 43 minutes [ 45780 ]
          Worklog Id 11155 [ 11155 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 day, 4 hours, 43 minutes [ 45780 ] 1 day, 6 hours, 36 minutes [ 52560 ]
          Worklog Id 11158 [ 11158 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 day, 6 hours, 36 minutes [ 52560 ] 1 day, 6 hours, 56 minutes [ 53760 ]
          Worklog Id 11158 [ 11158 ]
          tyson Tyson Phillips (Inactive) made changes -
          Time Spent 1 day, 6 hours, 56 minutes [ 53760 ] 2 days, 1 hour, 31 minutes [ 63060 ]
          Worklog Id 11163 [ 11163 ]
          tyson Tyson Phillips (Inactive) made changes -
          Description Plugins already support events by registering themselves during install/upgrade, which gets saved to `plugin_events` with a callback that is invoked when the event is triggered.

          We need an observer for the core to support events as well. I am thinking a new `events` table that supports the same events as plugins, which includes the event name and the path to the file to load, or the class defined by namespace (preferably).
          Plugins already support events by registering themselves during install/upgrade, which gets saved to `plugin_events` with a callback that is invoked when the event is triggered.

          We need an observer for the core to support events as well. I am thinking a new `system_events` table that supports the same events as plugins, which includes the event name and the path to the file to load, or the class defined by namespace (preferably).
          Automated transition triggered when Tyson Phillips (Inactive) merged pull request #444 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                15/Jun/18

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 1 hour, 31 minutes
                2d 1h 31m

                  Agile