We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
camunda BPMProject Type: software

camunda BPM

Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-9920

User operation log includes category

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.11.0, 7.11.0-alpha4
    • None
    • engine
    • None

      Categories:

      • admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios)
      • operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios)
      • Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios)

      Implementation:

      • I can filter the user operation log query by category (including multiple categories)
      • The category is persisted in the database (=> this should probably be covered an index, see CAM-10129)
      • old log entries remain without category and are not returned by the category filter => this means they will not be available in the new frontend
      • the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist)

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-9920

            User operation log includes category

            XMLWordPrintable

              • Icon: Feature Request Feature Request
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 7.11.0, 7.11.0-alpha4
              • None
              • engine
              • None

                Categories:

                • admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios)
                • operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios)
                • Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios)

                Implementation:

                • I can filter the user operation log query by category (including multiple categories)
                • The category is persisted in the database (=> this should probably be covered an index, see CAM-10129)
                • old log entries remain without category and are not returned by the category filter => this means they will not be available in the new frontend
                • the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist)

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        thorben.lindhauer Thorben Lindhauer
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              thorben.lindhauer Thorben Lindhauer
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              3 Start watching this issue

                                Created:
                                Updated:
                                Resolved: