4  Rel1 Version 1.0.0

The Task Order plugin is designed to configure and control the process of performing sequential and parallel tasks. Using a simple and intuitive interface, you can create rules that will block or allow certain tasks depending on current conditions. The conditions themselves are represented by a set of three elements. Where the main and dependent task and the type of relationship between tasks are described.

FAQ you can find here.

Plugin installation

To install the server plug-in, download the Task Order jar file.

Go to the "Application Settings" section.

Next, select "Download application" and choose the previously downloaded jar file.

Upon installation, the system will automatically create a Task Order User and a Task Order Administrator group.

Task Order User is a service user who is needed for centralized data storage of the plugin. In this case, these will be the rule settings for sequential and parallel tasks. The only action you need to do is connect the Task Oder User to the current project. For this purpose, go to  “Project Settings” - “Users and Roles” and in the “Administrators” section add the Task Order User.

To Start

To use the plugin, it is necessary that the user is in the group of the Task Order Administrator project.
For this purpose, go to the settings of the project users, these are the menu items: "Project Settings" - "Users and Roles" and in the "Users" section, add the user to the Task Order Administrator role.

Task order creation

New rules can be created via the tab Task order setting on the project page. 

After Tasks Order creation you will see information about on Reference Tab Panel on both Tickets:

This rule should contain at least one issue from the present project.
Tasks shouldn`t create a loop, it shouldn`t be a duplicate of a rule. 

Task Order Log

Task Order Log tab shows such information, like "Description" ("Add new rule"/"Remove rule"), "User" (who add or remove rule), "Rule" (the rule what was added or removed), "Date" (the date of rule manipulation), "Id" (the Id of an operation). All fields have a sorting possibility. Log has pagination. The maximum value of records on the one page == 10. Any action with the rule displayed in the Log.


Rel2 Version 1.1.

Task Order Clone

A new version of a plugin supports the rules cloning feature. The main idea of the function it`s a possibility to clone already created rules and connections. For example, some project contains parallel and serial tasks and a user needed to create the same type of rules with the same information and the same connections again. Instead of creating everything from scratch, the user can use the Task Order Clone function. The user should choose the needed rules (tic checkboxes)  and click "Clone" button.

 

That`s all, new rules have been created.

The important thing:

  • cloning rules created new issues with the same name, label, priority, and assignee, what the father's issues have;
  • cloning rules do not contain attachments, watchers, comments, and subtasks from father`s issues;
  • information about rules creation displayed on the "Task Order Log" page
  • rules from different projects have the same behavior

Task Order Log (changes)

A new version of a plugin has some UI and functional changes.

  • First of all, it`s a date range. Now a user can choose "Date from" and "Date to" values and get information by the chosen range.
  • Arise the opportunity to see more than 10 log rows on the page. The user can choose 10, 50 or 100 counts.
  • Search field under the date range search information by all log table. A user can input any value (date, time, rule id other stuff) and will see search information.
  • UI of the main table also was changed