Actively maintained

This module provides an input filter to display check-boxes that can be used as a task list. These check-boxes can be added using special markup when editing node content. When viewing node content, each task can be marked as "done" by clicking on the check-box to toggle it.

Drupal PM is a suite of Project Management and Work Tracking tools.

The suite contains several components, structured as separate Drupal modules:

• Organizations
• Teams
• Projects
• Tasks
• Tickets
• Timetrackings
• Notes
• Expenses

A specialist PM Permissions component provides granular ways of controlling which records are visible or editable for given Drupal users. Furthermore, Drupal PM is compatible with the Field Permissions module, allowing even greater flexibility.

Each component is structured in a manner that allows easy integration with other Drupal modules. For example, Drupal PM uses Field API for storing data and Views for displaying lists of data.

This module will delete any nodes of a certain node-type using the batch api.

This module provides single sign-on integration between Drupal and an Atlassian Crowd server. It supports detection of the Crowd SSO cookie to provide automatic login of users already authenticated via Crowd. Drupal accounts are created automatically if the user account doesn't already exist. The module also manipulates the standard Drupal user login form validation handlers to authenticate directly against Crowd instead of Drupal.

Some additional features are included that allow you to automatically associate Crowd groups with Drupal roles, redirect self-service user forms in Drupal (e.g., reset password) to remote Crowd alternatives, and more.

Importer module provides an easy way for creating database tables from various files. All variants of delimited text files are supports, and with an external class .xls files are also supported.

With this module the user can also insert new data into the existing table, provided that the number of columns in the table (not counting the primary key column) matches the number of columns in the file. If the ordering of the columns is not matched, the user can alter the ordering in which the data is inserted. Types of the appropriate columns in the table and the file are
displayed as means of ensuring that no sql error is generated (unintentionally).

If the user has a field in the data that should serve as a link to files in the file system, the procedure is as follows:

- upload the data to the database ensuring that the appropriate field contains
the file name of the file to which it should point

- zip all files that are relevant to the table

- upload files to the server using "Batch file upload" feature of the module,
making sure that appropriate table and field is selected

Uploaded files are saved in the directory of user choice under the files/ directory (it has to be created by this module). After this, the data in the chosen field are updated with the relative path to files uploaded on the server.