Project

General

Profile

Plugins Directory » Clear Plan

Author: Vladimir Pitin
Website: http://rmplus.pro/en/redmine/plugins/clear_plan
Code repository: -
Registered on: 2014-10-17 (about 10 years ago)
Current version: 2.4.4
Compatible with: Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x
User ratings:   (1)

Redmine Team Note
BEWARE: Commercial plugin!

«Clear Plan» — plugin for easy operational planning and control of execution in Redmine.

With plugin «Clear Plan» you can engage in operational planning in Redmine in sectional of executors, versions and months.
Each executor will have a personal work plan.


More information about our plugin

.


Plugin features

With plugin «Clear Plan» you can engage in operational planning in Redmine in sectional of executors, versions and months.
Each executor will have a personal work plan.

  • You will be able to prioritize tasks. Plugin «Clear Plan» allows you to change the priorities of tasks by simply drag and drop.
  • You will be able to approve work plan for the project and see changes that have occurred in plan after approval: what has changed in terms of execution, the estimated issue time, what issues have left the plan and what appeared in it, etc.
  • You will be able to control the work of a particular executor. Plugin «Clear Plan» allows you to view a consolidated work plan by executor, even if he is involved in several projects.
  • Plugin will provide you with detailed statistics of the plan execution sectional month and executor: how many issues and execution hours, percentage of the plan execution, etc.
  • You will be able to keep track of what stage your work hangs using an issue board. Which issues are in progress? Which are on check? Which are in queue? You can configure issue board on the basis of standard issue queries in Redmine.
  • Plugin «Clear Plan» allows you to determine which employee and in which issue status delays issue execution. You will have detailed statistics sectional issue and month.
  • Also, Redmine plugin «Clear Plan» provide a large number of small and useful options. For example: automatic issue binding to plan by execution dates, automatic creation of versions (stages), automatic plan closure, additional filtering in issue queries and more.

Plugin benefits against common Redmine

With the help of Redmine plugin «Clear Plan» you can plan and control the work of employees sectional both single project and all projects (cross-project operational plan).

With plugin «Clear Plan» you will always be able to control issues of employees sectional a single project, and also sectional all projects that involve the selected employee.

.


Plugin «Clear Plan» allow you to view changes that have occurred to operational plan after approval: what new issues were appeared in plan, what issues were removed from the plan, how changed the estimated time, issue execution time, etc. This option allows to increase control over the execution of the plan and achievement of key goals.

.


Issue board (similar to office board, which hang stickers) will help visually assess, at what stage and on which employees work freezes, where is the bottleneck, which accumulates the greatest amount of work.

.


You will be able to analyze the effectiveness and salaries of employees in the context of any time range: month, year or quarter.
Plugin allows you to configure issue movement stages. Each stage can be divided into columns.
Issue falls into a certain column on the basis of one or more Redmine standard issue queries. This allows to use wide opportunities of
build in queries to configure issue life stages.

.


With the help of Redmine plugin «Clear Plan» you can estimate correct setting of the issues lifecycle and compute employees, which freezes work. You will be able to view detailed statistics about whom, in what status and how long for issues freezes. Statistics can be viewed both by a separate task, and by all tasks sectional the month.

.


More information about our plugin Clear Plan

.

Changelog

2.4.4 (2018-09-04)

Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Fixed: stack level too deep
  • Fixed: fix double load environment

2.4.2 (2018-07-17)

Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Fixed: query on the statistics
  • Fixed: burndown diagram data collisions
  • Changed: visibility conditions
  • Changed: display shared versions in Plan manage tab
  • Fixed: order project versions in bulk edit

2.4.0 (2018-04-16)

Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Fixed: order project versions
  • Fixed: custom order of queried issues
  • Change: burndown chart improvements

2.3.8 (2018-01-31)

Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Added: call hook for internal use
  • Fixed: who can see allows to see issues from archived projects
  • Removed: custom menu link to WIP-diagram

2.3.6 (2017-10-11)

Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Added: support redmine 3.4
  • Removed: support redmine version below 3.4

2.3.5 (2017-07-10)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Added: setting "Default work plan"
  • Added: Added call_hooks
  • Fixed: Fixed bugs

2.3.3 (2017-05-15)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x.

  • Added: possibility to load pject settings via ajax
  • Fixed: queries order, now order everywhere where rendered list of issues by query
  • Fixed Burndown chart for IE 7 - 11

2.3.1 (2017-03-20)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • Added: The opportunity to set sharing versions for all projects by right in the role.
  • Added: Burndown chart
  • Added: custom orders for issue queries

2.2.9 (2017-02-02)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • performance improvement

2.2.8 (2017-01-24)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • fixed: duplicate order for trackers

2.2.7 (2017-01-20)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • fixed adding watchers

2.2.6 (2016-12-06)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • fixed approving full plan by user

2.2.4 (2016-11-11)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • fixed: duplicate values for who can see field
  • fixed: reverse migration

2.2.3 (2016-10-04)

Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • support redmine 3.3.0
  • hide\show statistics for all executors in project

2.2.2 (2016-09-14)

Compatible with Redmine 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • fixed bugs

2.2.1 (2016-09-13)

Compatible with Redmine 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • added cross-projects plan approving
  • added paatern by ratios for kpi plan/fact
  • fixed cross-project plan SQL for PG SQL
  • fixed mobile view
  • fixed PG errors

2.2.0 (2016-07-08)

Compatible with Redmine 3.2.x, 3.1.x, 3.0.x, 2.6.x.

  • added: hide\show statistics for all executors in project
  • added: rotate links for hidden sidebar
  • added: recalc counters after ajax update
  • fix for IE
  • fix: link versions to plans
  • fixed: postgreSQL queries

2.1.3 (2016-02-09)

Compatible with Redmine 3.2.x, 3.1.x, 3.0.x, 2.6.x, 2.5.x.

  • support new modal windows
  • fixed diff after plan was approved
  • fixed sorting
  • fixed relative links

2.1.2 (2015-11-09)

Compatible with Redmine 3.1.x, 3.0.x, 2.6.x, 2.5.x, 2.4.x.

  • fix integration with hierarchy

2.1.1 (2015-10-15)

Compatible with Redmine 3.1.x, 3.0.x, 2.6.x, 2.5.x.

  • added support for information about the license expiration

2.1.0 (2015-09-07)

Compatible with Redmine 3.0.x, 2.6.x, 2.5.x.

  • fix plan view
  • fix saving issues list after plan approve
  • fix changes for custom queries

2.0.0 (2015-07-10)

Compatible with Redmine 3.0.x, 2.6.x, 2.5.x.

  • support Redmine 3.0
  • added optional fields for plan history
  • added optional queries for plan

1.0.3 (2015-01-27)

Compatible with Redmine 2.6.x, 2.5.x.

Added compatibility with PostgreSQL

1.0.2 (2015-01-12)

Compatible with Redmine 2.6.x, 2.5.x, 2.4.x, 2.3.x.

1224ac0: * bugfixes

1.0.1 (2014-10-12)

Compatible with Redmine 2.5.x, 2.4.x, 2.3.x.

User ratings

  by Григорий Лактюков over 7 years ago