Details

    • Sub-task
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      task management-window

      • the user-management-icon and window will be changed to a task-management-icon and window
      • the task-management-window will have 2 tabs:
        • user-assigment (stays as it is and is the tab which is visible by default when the user opens the task management window)
        • task-preferences

      task-preferences

      • at the top the task preferences contain a select-form-element to select the workflow for the task.
        • When the flexible workflow-feature will be developed, all workflows designed in the workflow designer will be selectable here
        • For this feature the 2 hardwired workflows "default-workflow" and "ranking-workflow" (see below) will be selectable
        • Default is defined in application.ini on per-installation basis. Default of default will be the "default-workflow".
      • below this workflow-selection-element the task preferences contain a grid with 5 columns and the following column-labels:
        • workflow-step
        • user
        • target-columns(s): here is shown, which target columns are accessable for the user
        • visibility of column-labels
        • visiblity of non-editable target(s): here the handling of the non-editable target-columns is shown
      • By default the task-preference-grid only contains one row. Regarding the contents of the default row see below.
      • By clicking a button in the grid-header, rows can be added to the grid.
      • By clicking on a row in the grid, next to the grid a form appears, which allows to edit the contents of the columns if this row. This form has the following contents:
        • workflow-step-column: a select-form-element with all workflow-steps of the task
        • user-column: a select-form-element with all users which have been added to the selected workflowstep of the task and for whom no row had been added already to the task-preference-grid.
        • target-column(s)-column: one checkbox for every alternative-target. Checked means, the column is accessable. By default all are checked.
        • visibility of column-labels: A checkbox: yes and no. Default is defined in application.ini on per installation basis. Default of default is yes for normal tasks and no for tasks with the ranking workflow.
        • "visiblity of non-editable target(s)"-column: A radio button group of 3 radio buttons: "show", "hide" or "completly disable". Default is defined in application.ini on per installation basis. Default of default is "show".
          • the value is always is automatically "completly disable" on ranking step and not editable if the ranking step is selected in the workflow-step-column
          • If show or hide is selected, the user can change the visibility of the columns in the usual way in the editor.
          • If "completly disable" is selected, the user has no access at all to the non-editable columns.
      • By default the task-preference-grid only contains one row. It has special contents for the following entries:
        • workflow-step-column: "step default"
          • if this default row is edited in the form mentioned above, the workflow-step-column is not editable.
        • user-column: "user default"
          • if this default row is edited in the form mentioned above, the user-column is not editable.
      • If for all users/step-combinations a row has been added, the button to add a row is disabled
      • the task-preference-grid can not be filtered but can be sorted by user- and by workflowstep-column
      • on reassignment of a ranking task to a already ranked user: restart the task from the beginning, and delete already stored ranking statistics of the reassigned user
      • ensure that if multiple PMs editing a task to the same time, they get a version based midair collision error (like in bugzilla)

      Attachments

        Issue Links

          Activity

            People

              tlauria Thomas Lauria
              tlauria Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: