About Tasker

"Tasker" is application to track progress within project using either time estimation or agile style.
It was designed and implemented from scratch using Spring MVC 4 Quickstart Maven Archetype
While developing it whole code was stored on github and can be backtracked in GitHub page
To help build process it had it's own Q-Programming Jenkins page

Application creation process was started on May 18 2014 and over a year to have it in stable version

To quickly get to know with application, it's recommended to take
Tasker tours

If you found a bug, or want to propose an improvement , please go to http://q-programming.pl/tasq/project/TASQ and login using following credentials and create new task.

  • login: public
  • password: iFoundAbugOrImprovement

Application created by Jakub Romaniszyn http://q-programming.pl/ and is under GNU GPL License.

Application menus

There are two menus, one in form of navigation bar at the top and side menu to the left. Navigation bar presents basic information about time , event count and gives access to search , and user options. Sidebar menu have options to create and view projects and tasks and work with application in general

Go to Tasker tour for a quick overview of whole application menu options

Navigation bar
  • Search input box Shows all task with inputted text within task name, its description or tag. Additionally when user starts to type keyword, all similar task tags are shown in drop-down list. After user confirms selection, all tasks matching this criteria are displayed on Browse all tasks view , with query as one of filters
  •  2 Shows count of unread events. Click to navigate to events pages
  • Name Surname Personal menu under user's avatar
Sidebar menu
  •  Create task Here task or project can be created ( depends on user role)
  •   My project tasks - Click to search within active project for all tasks assigned to your account. Afterwards you can switch to other project, or add more criteria.
    More info on Browsing all tasks
  •   Projects Gives access to projects which are created or available for user. First are displayed 5 last visited projects.
    To show all , choose All projects
    Nearly every user can create his own project from here using Create new project
  •  Tasks - Gives access to tasks. Last 5 visited task are shown first, and all tasks can be shown using All tasks option
  •  Agile lists agile boards for last visited projects. All boards can be viewed using Show all boards
  •  Show all users - shows modal with all application users
  • Help (this page)

Personal menu

Under user's avatar there is Personal menu where user can basic options, notifications and watch screen.
If there are some unread notification, there will be number displayed next to user's avatar.
From this menu user can do following:
  • Settings - Shows users settings like language, theme etc.
  •  Events - Shows all system events
  •  Watching - Shows all currently watched tasks for logged user
  • Logout - ends current user session and logouts


Using this view, user can change some basic options regarding "Tasker" application.


By default avatar is set to lovely hamster. However it's possible to overwrite the default avatar with custom one. When user uploads new image and saves profile this image will be stored in app home dir


Here email notification can be changed. When user sings up into "Tasker" for the first time, notifications are marked as true by defaults.
If somebody don't want to receive any notification this checkbox must be de-selected


Whole "Tasker" app is "dynamically localized" which means that whole application can be easily translated to any language by translating messages properties file. On launch date only English and Polish languages were released, but any new requested language can be easily added with minimal development effort


Here user can change theme for application. By default blue "Default" theme is available, but application administrator can easily create new ones.


New users can be invited to use tasker, by using this form. Input valid e-mail address and click " Invite " to send predefined e-mail to inputed address


"Tasker" has notification system which will signal all important events within application. For example, If there will be some administration activity related to user's account. A system notification will be sent.
Each application user can   Watch project, to track all events related to project he finds interesting. If there will be something new in project(comment, new file or task status update), new notification will be then added to account. After each page refresh, application checks if there is new notification and adds unread count next to user's avatar.
For example, If there is one unread notification  1 will be shown next to user's avatar.
In order to view all notification click it, or  Events (1) must be chosen from Personal Menu
In this screen we can view unread ones ( bolded ) mark all as read or delete all.


It's possible to sign up for watch notifications about task. If it will be edited , some user will add new comment or state of it will be changed, all users who are watching this project will receive in-system notification.
Furthermore if user selected "Mail notification" in My settings, he will receive email notification about watched event
In order to sign up for project notification press watch button while being in task details screen.
All currently watched tasks are displayed in  Watching view which can be accessed through Personal Menu
To stop receiving notification about project, press stop watching button located inside task details or in Watched screen inside Personal menu


Each user that registered into application can be viewed in modal User window shown after clicking  Show all users option in sidebar menu
Every user is shown in this view with his avatar.
Additionally if user is online ( logged into Tasker and performed action within 15 min)   will be shown next to his name.
From this screen we can sent e-mail message by selecting icon message as well.


Browsing all projects

Each user can view project to which he is assigned ( or is admin ) To do so, please select All projects from   Projects menu

On this screen every project into which user is assigned is shown here. Basic information like name , description and who is main administrator of project is displayed.

Project that are set as active are highlighted and icon is shown in active button. When creating new task, active project is always taken first. To change active project, please click button in corresponding row

View projects details

Take a quick  Project details tour

In order to show project details , please either select it from   Projects menu , or click on Project ID , on task screen.

Project details screen all project information related to this project

  1. Project Name
  2. Project description
  3. Open/Ongoing/Closed tasks - Progress bar showing ratio of open/closed tasks within project
  4. Open/Closed Chart - shows how work was done in project. How many tasks were created and closed
  5. Show more than 30 days on chart By default events from last 30 days are shown on create/closed chart. If you would like to view all events, from very beginning of project, click this checkbox. Please be aware that rendering this chart can take some time, depending on how many tasks were within project
  6. Latest events in project
  7. Events list pagination
  8. Tasks list
  9. Hide closed tasks - by default closed tasks are hidden in this view. In order to view all task de-select this checkbox
  10. Show all/hide all Subtasks - if one of tasks have subtasks icon will be shown before it's name. After clicking this button all subtasks for every task will be expanded
  11. Project participants - Show modal with all project participants
  12. Activate/Deactivate project - set displayed project as active. It will be used while creating new tasks, listing and searching as first choice. It will also be visible on left side menu
  13. Project management - set up project, add new users, set admins etc.

Creating project

In order to create new project if you have correct role, start by selecting Create new project option from sidebar menu.
This will show you "New project" creation screen on which all details about new project can be filled in

Project ID Unique ID of project. This will be used when creating new task to generate its ids.ID should not contain any numbers and consist of maximum 5 letters. Chose wisely as it won't be possible to change project ID after it has been created
Project name Name of new project. It must not be empty. It can be changed at anytime
Agile type of project Choose agile type of newly created project
  • SCRUM with more focus on creation of new features or even whole new project
  • Kanban good choice for already existing projects with maintenace phase
Project Description This section should contain description what the project will be about, what's its goal, and how the project will be created. If project will use some technologies or some new solutions it's recommended to describe them as well. When creating new project this field can't be empty

Editing and managing project

Each project after it has been created can be edited. To manage your project click on project details screen

Default project settings

After project has been created you can edit it's name or description by clicking icon next to project name.
It's impossible to change ID of project, once it has been created Task progress in project

Tasker has two option two track progress within project.

  • Estimated time tracked - Each task before "sprint" is started, should have estimated time set right away. Sprint is in quotes on purpose, as if time tracked it's not completely SCRUM anymore. Regardless this option can still be used to track progress for team
  • Story points recommended for agile projects. Each task then is measured with points - which measures complexity of this task. More on story points

Please note that it's not recommended to switch how progress is tracked while project is ongoing or has already some sprint which were tracked. This can cause some errors and very odd charts in reports

Default task priority

Every new task created within this project will have this priority. Of course it can be freely changes by user

Default task type

New task created for this project will have this task type. It can be changed by user before creation is finished

Default task assignee

When new task will be created chosen user will be inputed into assignee field. If user would like to assign someone else , he can choose him/her from autocomplete field on task creation screen



All project admins are listed in here. Project admin has access to this screen, plus additionally can perform any operation on tasks within this project to maintain order etc.
To add new project admin , user first has to be added to project as member. Next click in his row. If user is already admin and you would like to remove this privileges from here , click button located in same place but with minus symbol : Project members

Every project member is listed in here ( with Role in parenthesis). To add new existing user into project click . This will show field with autocompletion of all application registered users. Choosing one of names will automatically start process of adding user to project. To browse through all application users click button either next to add button on located in top menu next to avatar.
To remove user from project , choose button in users row


Browsing all tasks

Take a quick  Task list tour to get see how list can be filtered etc.

To browse all tasks select All tasks option from  Tasks menu

By default all open tasks from currently active project are shown. To show tasks from other project choose it from dropdown list( only your project are listed here )

Displayed tasks can be filtered by priority or status.
In order to filter by priority select caret() near Type text in table header
To filter by status , select it from drop down menu in Status also in table header.
Each applied filter is shown next to Task Project combobox, and can be removed by clicking symbol

If Task has any subtasks symbol will be shown next to it's ID. Subtasks can be expanded manually for each task with subtasks, or by clicking Show all subtasks in top right corner, just below export button

From this view user can also Export tasks by clicking Export button

View task details

Take a quick  Task detail tour

  1. Project ID/ [ Task ID ] Task name
  2. Current task status - in order to change this status click and choose new one
  3. More about task statuses
  4. Task priority - to change click and choose new
  5. Tags - to add new tag , input it. If there is similar tag, autocomplete box will popup. To remove tag , click symbol
    To view all tasks with this tag, click it. This will move you to Browse all tasks view with applied tag filter.
  6. Task description
  7. Story points - if task is estimated, story points for it will be shown. If no points were set ,question mark will be shown instead. This value can be changed either from Edit menu, or from this view quickly by hovering over ? to reveal extra button .
    Click it to show input field Confirm it by either enter key, or clicking check-mark sign. Cancel input by clicking x
    You have to be either task owner or project admin to do so
  8. Log work button - use it to log time spent on this task. More information in Working with tasks section

     Keyboard shortcut 'l'

  9. Start timer button - starts/stops active timer on this task
  10. Time bars - shows how much time was estimated, how much logged and remaining
  11. Related tasks - Shows list of all task that are related/linked to it. In order to add new link , press button ( this option is also available under edit menu)

     Keyboard shortcut 'r'

  12. Subtasks list - all subtasks are shown here with type, priority and progress. To create new subtask , click button ( option available from edit menu as well )
  13. Activity log tab - click to show all activities related to this task
  14. Comments tab - click to switch to comments tab. All comments related to this task are listed ( sorted from newest).
    New comment can be added by clicking button

     Keyboard shortcut 'c'

  15. Show edit menu - more information in Editing task section
  16. Start/Stop watching task
  17. Delete task - deletes this task ( project admin only) More information in Removing tasks
  18. Task owner and current assignee - you can quickly assign someone to this task by clicking button.
    This will show modal window. Start typing username to show autocomplete hints with all project members

     Keyboard shortcut 'a'

  19. Creation, last update and due dates
  20. Sprints - if task belongs or belonged to one of sprints, it will be listed here

Creating tasks

To create new task, click Create task in sidebar menu
This will show you "Create task" creation screen on which all details about new task can be filled in.

Summary Brief summary of what this task will be about
Description Description of task. All information required to finish it should be placed here. Basic styling is available through built-in rich text editor
Project Project for which this task will be created.By default user's active project is always selected
After user select project , task type and priority will be automatically updated to default project value ( overriding already selected value)
Assign User to whom this task will be assigned. Autocomplete of all project users is added in this field. If input box will be blank , task will be unassigned. Project default assignee is always entered when this screen is viewed. Default assignee can be changed on Project management screen
Type Type of task. This helps to filter task for whole team. Additionally types like "Task", "Bug" and "Idle" have estimation disabled by default. Project default task type is always selected when this screen is viewed. This can be changed on Project management screen
There are following task types available:
  • Task - a simple activity. Usually not too big, and most of the time without fixed estimation. It can also be used to group other task ( by linking as related )
  • User story - feature, case scenario or bigger thing to be done. In most cases before work has been started on it , it should be estimated
  • Issue - used mostly report that something is not right within project but not might not be bug at all
  • Bug - if something is broken, task of this type can be created
  • Change request - in case customer would like to change something which was not part of initial scope, or there is some feature request to working project
  • Idle - sometimes it can happen that team is not working, waiting for something to be unblocked, or just waiting idly for new tasks
and types for subtasks:
  • Subtask - most common subtask type
  • Task bug - If there is some bug related to task , we can either create new bug and link it or create subtask with this type
  • Idle
Priority How important this task is
Sprint If there is already existing sprint which is not yet finished , newly created task can be added right away after creation by selecting it from combobox. Please note that if sprint is active, its scope can change
Estimate Time estimation of how much this task can take. Standard format should be used : *d *h *m (days, hours, minutes ; where * is any number ).  If only number is inputted , default (h) hours will be used. Also values longer than 4 weeks ( 28 days ) will be rejected as it's not reccomend to plan so long tasks , and they should be splitted to smaller once
Story points Complexity measurement of newly created task. This value can be changed later on via Edit menu, from Details screen , or from Backlog view
More on story points

 If task is not estimated, have no points , or optional estimate time, please select Task without estimation checkbox.
If selected this task can be added to sprint ( even active ) and not affecting sprint scope.

Due date If task should be finished before some date, enter this date here. Tasks from user's projects, with due date soon to present day are shown on home page
Files Choose files that you want to add to this task. This can be some documents, excel sheets or image
In order to add more than one file, clicking  Add more files button will add extra slot for it. Attached files are shown on Task detail screen. If file is an image, it will be shown as thumbnail

Editing tasks

If user has permission to edit task , extra button will be shown on Task details view (14).
Following actions are available:

 Edit task allows user to edit already existing task. Each change will be logged and can be reviewed by task "Activity log".
 Please note , that if task is in already started sprint, changing story points value will affect sprint scope
 Link starts linking process. If two tasks have something in common, blocks or are duplicating. They can be linked . Every linked task is shown on task details screen.
To link task , start by clicking this menu action, or button. Choose link relation, and then start typing in field ID or name of task that should be linked
 Add subtask shows create subtask screen which is nearly the same as regular task create screen , but without story points section
Create linked task starts creation of new task but automatically will link newly created task with currently shown one.
Additionally new task's project will be locked to current task project.
If task is closed this option will be shown as extra button
 Attach file allows to add files ( documentation , pictures , excels ...). The same action is available via button ( shown only if there is at least one file attached )
 Convert to task (subtask only) converts one of subtask into regular task.
New next free project ID will be assigned to it. Additionally both task will be linked with "relates to"

Removing tasks

Sometimes it can happen that task needs to be deleted. This is not recommended course of actions, and in most of the times task should be updated, renamed to match desired state. If task needs to be deleted, only project administrators can perform this operation.

Please be aware that removing task should not be used for tasks in active sprints etc. and it should be used in very rare cases

Removing task will purge all worklogs, comments, files and subtasks. Only worklog information about task removal will be added for project.
All other information will be lost and cannot be restored!

When deleting task, if other users are still working on it ( have active timer ) they will be listed.
If user has role 'Power User' he will then be able to "Force delete" task which will stop all active timers and remove task.
After deletion assignee and task owner will be notified about that event (if current user is one of those , he of course won't recieve notification)

Importing tasks

If there is a need to create more than one task, instead of manually adding them one by one, there is possibility to import them in one bulk.
In order to import tasks, navigate to Task create screen and choose Import tab.
Here we can either import previously exported file ( either excel or xml) or download template and fill task in it.
After file will be completed, it can be then imported using that screen.
Every new task will have assigned new ID , based on which project was chosen

 Please remember to choose project into which new task will be imported. By default , user's active project is always selected.

Exporting tasks

If there is a need to transfer task from one project to another or move it to another server, then can be exported using Export button from All tasks screen.
Clicking it, will reveal checkboxes next to every visible on screen task. All selected task then can be exported either to excel or xml file.

 Information like: task ID, comments, attached files and worklog is not transfered into exported file in current version

Working with tasks

There are couple ways to work with task within application. All depends on team agreements and there are no stiff rules how to work with task.
However there are couple recommended things and some rules.

  1. Before starting working on task it should be estimated ( either time or story points if working in agile)
  2. Tasks can be worked on without sprint, but tracking whole project will be then more difficult
  3. When sprint was started and one of team members would like to start working on it, he should be assigned to it ( either by project admin, or himself using Assign button)
  4. Add tags to help categorize project tasks better ( only project administrators, Administrator or task owner)
  5. If project is time tracked, work should be logged. It can be inputed manually by using Log work
    If project is Scrum based, time can still be tracked, which is very helpful especially on earlier stages of project to correctly map how much time is consumed on tasks
  6. Include files , docs or pictures to help developer understand task
  7. Task type is very good to group many other tasks/user stories. After creating it , all tasks can be linked with "relates to" link type
  8. To stay up-to-date with tasks changes , subscribe as Task watcher , using button Task details view(15)
  9. Comments are very helpful to post more information or indicate what has been done on task

Logging work

To help better track project it's recommended to track time for each task, regardless if project is time based or Scrum type.
Time can be logged either from task details page , or directly from Agile board. Click button to show logging modal window.
On it , input how much time was spent on this task in format *d *h *m (days, hours, minutes ; where * is any number ).
It's not possible to log more than 5 days at once to force user to log work daily
If work was done in other date ( for ex. yesterday ) , mark correct date and time in Date and Time fields.

By default remaining time will be automatically reduced, or it can be manually set by selecting Set manually radio button and inputing remaining time ( same format applies).
The remaining time can never be less than 0.
If more work was logged in task, it will be marked on task detials screen accordingly.

Task status

Tasks can be in following statuses:

  •  To Do - new task, which can be taken by developer
  •  In progress - some work has been started on this task.
  •  Blocked - task on hold, because one some issues are preventing from continuing work on it
  •  Completed - task has been completed, only some review or testing left to be done
  •  Closed - finished task, all work done


If user would like to track time in real time, timer can be set for task.To do so , click button. This action will start timer ( Information about active task will be shown at the bottom of screen). To stop it click button located on page bottom or on task details page. Timer will also be automatically stopped ( and work logged ) when task is closed. Please note that it won't be possible to close task if there is other user's active timer on this task

 If more than one day is on timer , user will be redirected to task page and timer canceled, because it's not possible to log more than 1 day at once. Please remember that Tasker uses 8h = 1d conversion. This can be changed by admin


Sometimes task can have multiple things to be done within.
In order to better track to do list , subtask can be created for it.
Subtask is just like regular task, but without story point estimate , and is permanently linked to parent task.
It's creation process is done via Edit menu

Substaks can always be converted to regular task using Edit menu. It's impossible to do other way

  Time logged within subtasks will always be added to it's parent task.


Main feature in Tasker is a way to track project progress using agile methodology. When used correctly, it can provide very good work feedback, help to plan future features and present big picture on that project.

When project is created, it's type is set ( this cannot be changed after creation). Base on this type , correct board will be always shown for end user.

Under Agile main menu, last visited project boards are listed (+ active project's board in bold) and additionally all users project's boards are available under Show all boards menu option


SCRUM is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during production processes, the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team's ability to deliver quickly and respond to emerging requirements.[source]
SCRUM should be project chosen methodology, if there are many things to create from scratch, lots of new features and some bugfixes. It's very good in tracking how team progresses within new areas or known ones, but with new project

Story points

Each team can freely translate how point is translated to work time. It's important to remember that 1SP is not necessary 1h!
To find 1 story point, try to take one of finished stories which was smallest and quickest to do and try to estimate other based on hom much work is needed in them.
Available values of story points is modified fibbonaci sequence : 1, 2 ,3 ,5 ,8 ,13 ,20 ,40 ,100 where points above 13 indicate that story is big and could possibly divided into smaller onece


All tasks to be done, or in progress in selected project are displayed here. This is main planning view, on which project administrators (for ex. Scrum Master or Product Owner) can plan future work , and set its priorities

  1. In order to create new sprint , click create sprint button. This will create sprint with next number, and allow to add tasks into it.
    After creation, this sprint will also be shown on task creation screen, allowing to straight away add new task to it.
    This sprint won't be active until it's started.
  2. To start sprint , click button , which will be shown, when hover over sprint. This will show Start sprint modal , where sprint start and end date must be inputed.
  3. To end sprint, click  Finish button , shown on hover of active sprint.
    All non-finished tasks from that sprint will be moved back to backlog, and then can be added to next sprint.

Sprint cannot be started if within it, there is at least one task which is not estimated ( unless it has "Task without estimation" marked on Create/Edit view)

Start date is always taken when generating reports. End date is for team information, and will be overwritten with correct end date and time, when sprint will be ended

There can be only one active sprint at the time. Also sprint start date can't overlap already finished sprint's end date


All task that are not yet done, and not assigned to sprint ,are listed in this section of backlog view. When new sprint is created drag and drop tasks from this section, to assign them to it.
You can order tasks based on how tasks are imporant, so that in next sprint they can be taken as first.
To order tasks drag and drop them, and confirm new task order by clicking  Save order button
Additionally right clicking on task will show context menu , on which we can assign this task to one of existing sprints, or move this task to top or bottom of backlog. Moving to top/bottom of backlog still requires confirmation of new tasks order.


This is main agile view for the team. All tasks, that team supposed to work now, on are listed here. Each task is presented in form of card with information like name, task type, story points progress and current assignee.
Following actions are available:

  • Change task state - drag and drop task from one section to another to quickly change it's state, without a need to enter task details
  • Assign task - if tasks is not yet assigned to anyone, you can assign it to one of team members. Click button on task card to show Assign modal window
  • Log work if currently logged user is assigned to one of task, he/she can log time spent on this task from this screen clicking log work button in task card.
  • Filter tasks by tags Next to Sprint number and date , all tags for tasks within sprint are presented. You can filter task with this tag , by clicking it . Click it again to reset tag filter ( or select another to filter by it now)
  • Order tasks as on Backlog view , tasks can be ordered to indicate which task is more important. To order, drag and drop task within "To do" column , and confirm new task order by clicking  Save order button


On this view summary of each sprint is presented. By default last ( or active ) sprint is shown

Burndown chart
Shows how team was working on assigned tasks. Remaining line should always be near "Ideal" . If it stays above, it means that team is either not working efficiently, or task was underestimated in story points. Staying below means the opposite. In case of bad estimation it should be adjusted in next sprints. All in all, at the end of the sprint Ideal and Remaining should meet.
If project is time based, instead of story points , estimated time will be taken to count remaining/burned time
Logged time
This chart shows how time was logged per day on whole project
Events in sprint
All sprint events like creation of new tasks added to sprint, work logged or closed tasks are listed in here. Events like comments or task creation for project are omitted on this view as not relevant to sprint
Sprint summary
This tab summarize how many task were completed ( and their story points value) and which were not. Also total time spent on tasks in this sprint is added and shown here as well


Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members. In this approach, the process, from definition of a task to its delivery to the customer, is displayed for participants to see. Team members pull work from a queue. Kanban in the context of software development can mean a visual process-management system that tells what to produce, when to produce it, and how much to produce - inspired by the Toyota Production System and by Lean manufacturing.[source]


Main view for Kanban. Most of team work will be done on it. For actions that can be performed please refer to Scrum board section they are generic

The only one big difference compared to Scrum is, that Kanban don't have sprints. To track milestones we use releases in it.
Release indicate that some bigger part of changes, features or bugfixes has been done , and it should be delivered (for ex. to client)

To create new release, click  New Release button which is available for project administrators on Project details page.
Clicking it will show modal window, where name of release and optional comment can be inputed. After it , all closed tasks will be moved to this release , and new release will be started.
From now on, closed tasks from that release will be hidden, and can be reviewed on reports page only. It can be reopened, but then it will be part of new release


On this view summary of each release is presented. By default last ( or current ) release is shown
Burndown chart
Shows how team was working on during releases. Main chart shows how many tasks were open/in progress/closed in given time frame
Logged time
Time logged in project in selected release
Events in release
All release events like creation of new tasks, work logged or closed tasks are listed in here. Events like comments or omitted on this view as not relevant to release
Release summary
This tab summarize how many task were completed with time spent. Total time spent on all tasks in this sprint is added and shown here as well


In order to not mess up application each user has application role assigned to keep things in order.
Following roles are available

Administrator All below and
  • Edit any project
  • Assign users to any project
  • Add to project administrators
  • Edit any tasks
  • Change state and priority of any task in any project
  • Delete task
Power user Power user
Can do all below and
  • Edit project to which he is assigned
  • Assign users to project (if is project admin)
  • Add to project administrators (if is project admin)
  • Edit tasks in his projects
  • Link tasks in his project
  • Start/stop sprint if is project admin
  • Perform release if is project admin
User Regular user
Can do all below and
  • Create tasks in project in which he is assigned
  • Edit tasks he created
  • Change state or priority of task he is assigned or created
  • Comment on task which is not in Closed state
Viewer Demo user
  • Login into application
  • Change user settings, add avatar
  • Watch tasks
  • View all users in Tasker
  • View tasks in project he is assigned to
  • View Task activity log
  • View agile boards, reports and backlog
  • Invite new users to application

Additionally in order to edit task ( change name, description, add tags ) , user have to be either task owner, Administrator or project administrator

To work with task (change state, log hours ) , user have to be task assignee or Administrator

Tasker v. 1.3.2
created by Jakub Romaniszyn http://q-programming.pl/ and is under GNU GPL License.