Language:
English

Project possibilities

Project possibilities

Projects allow to combine tickets (tasks) and group them into subprojects, that is organize a hierarchy of projects (Project -> Subproject -> Task)

This is not the most important thing, however, as the main advantage of projects is in the possibility to organize a team work:

  • Access for all team members to all the tickets within a particular project (available to this team). For example, when a new member is added to the team, he/she will acquire access to all tickets without even having direct messages
  • Access for all team members to internal (private) ticket discussions. For example, any team member can know the actual ticket status and opinions of his/her team on the task
  • Clear understanding what tasks your team is responsible for. Tasks marked as red and yellow are on your team side, tasks marked as green are on another team side. For example, if there are two teams in a project (Executor and Customer) it is easy to understand how many (and what) tickets are on the Customer side (that is they require some precision or acceptance) and on the Executor side (that is they require an action or a reply)
  • Disconnecting users. In the standard version (withou using projects and groups), if someone received a message in a ticket, he/she will always have access to that ticket. If you use project groups, then after deleting user from the project team he/she will lose access to tickets in this project.

Settings. Project list

Here you can view project list which are administered by you (full list of available projects can be viewed from the menu of a project and in a separate task)





Project details

This is the page of project settings. The most important setting is the project groups. Groups can customized for each project. To add a user to a group, simply put in his/her e-mail (if the user is not in the system, he/she will receive an invitation letter).

Users of one group have access to project tasks and to internal messages of other members of their group. Each user can enter only one group within a project. Each group must have one responsible person who will receive tasks which are assigned to the group (group members are hidden from other group members).