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

In Cockpit, on process instance view in jobs tab some columns cannot be sorted

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • cockpit, engine
    • None

      Components

      https://github.com/camunda/camunda-bpm-webapp/tree/master/ui/cockpit
      https://github.com/camunda/camunda-bpm-platform/tree/master/engine-rest/engine-rest
      https://github.com/camunda/camunda-bpm-platform/tree/master/engine

      User story

      In Cockpit on the process instance view and the jobs tab (see attached screenshot), I want to sort results by creation date and activity to navigate the result set better

      Background

      The properties exist already in the results, but cannot be used for ordering in Java API, REST API or Cockpit.

      Acceptance Criteria

      • The JobQuery in the Java API is extended by ordering options for activity and creation date
      • These properties are exposed in the REST API
      • The jobs tab in the process instance view allows to apply this sorting

      Implementation hints

      • See the subtasks linked to this ticket

        This is the controller panel for Smart Panels app

          1. job-tab.png
            job-tab.png
            82 kB
          1.
          		 In the Java API, I can order job query results by activity and creation date Sub-task Closed Unassigned
          2.
          		 In the REST API, I can order job query results by activity and creation date Sub-task Closed Unassigned
          3.
          		 In Cockpit's process instance view, I can order jobs by activity and creation date Sub-task Closed Unassigned

            [CAM-9877] In Cockpit, on process instance view in jobs tab some columns cannot be sorted

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important

              Unassigned Unassigned
              tassilo.weidner Tassilo Weidner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: