Uploaded image for project: 'Hawkular Alerts'
  1. Hawkular Alerts
  2. HWKALERTS-131

Persist member trigger dataId mappings for re-use on condition updates

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.2.Final
    • Component/s: API/Model
    • Labels:
      None

      Description

      It can be difficult to construct dataMemberIdMaps when updating conditions on group triggers. To make it easier on the client writer, when making condition updates that don't introduce new dataIds (like when just changing a threshold value on an existing condition) don't force them to supply the dataMemberIdMap and re-use previously provided mappings.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jayshaughnessy Jay Shaughnessy
                Reporter:
                jayshaughnessy Jay Shaughnessy
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: