This project aims to create a project management tool based on Scrum principles on top of Drupal and the Case Tracker module(on it's 2.x branch, based on entity types).
Initially, the idea is to provide a scrum board and some Scrum specific fields and reports, but feel free to give feedback and share your thoughts
This module provides functionality to maintain a pool of task templates in ERPAL. These tasks can be cloned into you project to get a quick project setup. It is also possible to set tasks to "Clone as default task in every project". After this setting, these marked tasks will always be created after a new project has been inserted. This will save time in the project kick-off as recurring tasks in every project like "project management", "Set up team" e.g. will be automatically created.
This module requires erpal_project_ui to work.
More information to come soon.
This module provides project rating functionality for controling. With this module we will show red, green and yellow lights on tasks and projects. These lights give a signal about how the project develops. You can add these lights for different categories such as "administration", "budget", "timeline" and add rules when a penalty (or rating) will be added to a task or a projects. This makes it possible to get an overview over complete projects and simple tasks and their progress.
More information to come soon.
This module packages and distributes projects hosted on GitHub in a manner compatible with Drupal Core's update module and drush's package management system. As long as you maintain your project on GitHub using the same branch and release tag naming conventions used for projects on drupal.org, those projects will be registered, re-packaged, and available via your website.
This module provides functionality to automatically create tasks. When a task will be repeated can be set in the advanced section of a task edit form in the fieldset "Repeat Options" . You can determine the date of the first repeating process and a repeating rule to clone a task for example every day, every week and so on. This will be done with ical rules.
Furthermore you can enable repeating of subtasks to clone subtasks also. The deadline of the task will be changed according to the "Increase repeated deadline" setting.
This module requires erpal_project to work.
Checks a spreadsheet of content type/fields against the site's current configuration.
Module for auditing the configuration of contrib and custom modules in the system.
State Transition Control (STC) module enable workflow control on select list fields. If you enable state transition control on a field, you can set each (current) value of this field that which values can be set in next time (if the field current value is a particular one).
This module can be very useful in case trackers or in any other complex systems where it's necessary to control the value transitions of a select field (ex.: an administration field).
Requirements:
Features:
This module is the container for customized code for a site. It must be used in conjunction with Codit.
Codit: Local should reside in the site specific module directory as a 'local' module for just that site. It should not reside in sites/all or be used as a git submodule.
This module provides the container for site specific elements like
Intend to replace all the permission handling that is carried out by PM Module.
Under Development.
Assumption.
1. There is only one single parent reference field.
2. User is Drupal user and not pmperson.
Requirement for testing.
