Administrator's Guide

How to configure control rules for users to access operations and custom fields in the workflows

How to configure control rules for users to access operations and custom fields in the workflows
You can configure the control rules for users with a particular role to access the workflows (execution of operations for these workflows) and to access the custom fields .

Access control rules for operations

How to configure permissions for users in operations

You can configure the rules as per which the users with particular roles can or can’t view the operations, execute them and become assignee for the task at particular stages of its workflow. To set the access control rules for operations, choose the required operation from the list and select the tab “Operation Permissions”.

Settings of each of the rules are given in the form of pairs of roles lists. Users with the roles from the left list can not execute the particular actions, and the users from the right one can do this.

How to create a new role

So as to register a new role in the system:

  • In the menu, go to the Users Management
  • In the menu, go to the page "Roles"
  • Press the button "Create Role" in the panel of roles list
  • In the menu that opens, enter the role name. Specify the option, if you need to place a button for creation of user with this role on the dashboard.
  • Press the button"Save"

How to Manage Roles of Users

As a rule, there is no term like group of users in TrackStudio. Generally group management in incident management systems means that the administrator creates some group, e.g. "Developers" and goes on adding users like Tom and Dick (and remaining 325 developers). Thereafter he configures the permissions for this group for some project (it is reasonable enough, as configuring permissions individually for users will be quite costly). When you have 2-3 developers and a couple of projects — this is the most convenient way for setting permissions.

Custom field of type String


One string, being entered by the user


String is limited to a length of 1800 characters (by default the value is limited to 200 chracters) and corresponds to type String in Java. On edit form it is represented by an input string <INPUT type="text">, or, by an input string and drop down list when an alternative script is used.

Custom field of type Date


Date and time, to be entered by the user.


How to add custom fields in Tasks

In TrackStudio, with the help of custom fields you can store specific information about your tasks in structure form. Custom fields can be attached to tasks, users, or to workflows.

The fields, attached to tasks or users, apply to analogous entities (sub-tasks or subordinate users) lower in the hierarchy. The fields, attached to workflows, apply only to tasks, corresponding to the workflow (in this case the tasks can be of different categories).

Types of fields

Configuring integration with Perforce

Installation and Configuration of Perforce server

Perforce is a commercial, proprietary revision control system developed by Perforce Software, Inc. One Perforce server can simultaneously have several repositories, called as depot.

Perforce server can be installed in operating systems Unix, GNU/Linux, Mac OS X, Microsoft Windows. We have described the installation and configuration of Perforce in GNU/Linux for testing the capabilities of TrackStudio.

Integrating TrackStudio with Josso

JOSSO, or Java Open Single Sign-On, is a solution based on J2EE open source code for centralized authorization and authentication of users for applications.

  1. Download the executable files of JOSSO server
  2. Unpack them.
  3. In the terminal or command line, go to the folder, where you unpacked josso
  4. Go to the folder ‘bin’ inside the folder ‘josso’.

Integrating TrackStudio with Atlassian Crowd

Atlassian Crowd is a web-application for managing the account details of users in different applications, implementing the Single sign on mechanism.
TrackStudio supports the authorization of users through Crowd. In this article, we suppose that you already have Crowd server installed and configured, and the accounts required by you have been created in it.

Configuring the integration

  • Start Atlassian Crowd server, if it has already not been started.
Syndicate content