Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
The Frequently Asked Questions (faq) module allows users, with appropriate permissions, to create question and answer pairs which they want displayed on the 'faq' page. The 'faq' page is automatically generated from the FAQ nodes configured. Basic Views layouts are also provided and can be customised via the Views UI (rather than via the module settings page).
This module has not been ported to Drupal 8. Refer to this issue to find out its progress.
Distributions contain a carefully selected set of module versions along with specific patches that have been tested for compatibility. These projects and their versions are defined through .make files within the distribution and their projects.
Individually upgrading a project could potentially break the distribution and should be avoided unless you are an experienced developer.
However, unlike those modules which have the available fields hard-coded, this module allows you to edit any field on a content type and check "Enable altering this field from comments"!
By using only standard Drupal components like Fields and Views, you can construct any variety of full-featured bug trackers, customer support, sales or project management tools.
This is most similar to Comment Driven (for Drupal 6), except (1) it's available for Drupal 7 and (2) it's design is much simpler! Rather than inventing lots of new code and APIs, Comment Alter strives to integrate with other modules (like core's Node module to store the changes as new revisions and Diff module for displaying the changes made in a particular comment).
Besides core modules like comment.module, the only dependency is Diff module.
This module has not been ported to Drupal 8. Refer to this issue to find out its progress.
A Work tracker for Open Atrium 2.0 (similar to the Case tracker in Open Atrium 1.0) which allows you to create Tasks in order to collaborate on work.
Work Tracker is designed to fit seamlessly into the way Open Atrium 2.0 works and it’s paradigm for flexibility. For example, Work Tracker has no concept of “projects” - instead it groups Tasks together using Open Atrium Sections, which allows users to define for themselves what a “project” is in a way that best fits their organization.
Suggestions, bug reports and patches are welcome in the issue queue!
Install OpenAtrium 2.0 (version 2.0-rc1 and later install Work Tracker by default!)
Create a new Space
Create a new Section inside that space, and select "Tasks Section" under "Section Type" (it's below the body and "Weight" fields).
Using the add button in the header (looks like a '+' sign), create a new Task!
Complex websites and web applications can be created by combining configurations of Modules, Content Types (CCK,) Views, Panels, Menus, Blocks, Categories, Roles / Permissions, etc. This site setup and configuration process is a very time consuming and repetitive bottleneck.
Patterns module is built to bypass this bottleneck by managing and automating site configuration. Site configuration is stored in XML or YAML (requires SPYC YAML parser, which needs to be downloaded separately from http://code.google.com/p/spyc/) called Patterns which are easy to read, modify, manage, & share and can be executed manually or as a part of an automated web site deployment.
Drupal PM is a suite of Project Management and Work Tracking tools.
The suite contains several components, structured as separate Drupal modules:
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.
BugHerd is an issue tracking system built for designers and web developers. This module allows you to quickly and easily add BugHerd to your Drupal site. The module allows you grant access to BugHerd by roles and even turn it off for admin pages.
The Maestro module is a workflow engine/solution that will facilitate simple and complex business process automation.
Maestro has a workflow engine that executes templates created using a visual workflow editor. The workflow engine runs in the backgound and executes the workflow tasks, testing the tasks execution results and branch the workflow if required. The workflow engine will run every x seconds and execute all tasks that are in the queue which have not yet completed. Once they execute and return a success status, the engine will archive them and step the workflow forward. Both these components have been developed to support any number of different task types.
Maestro has been built to be extended with new task types and now contains tasks that are aware of webforms, entityforms, content types, rules, triggers. Custom interactive functions and batch functions can be added for custom business logic or integration.
The following is a summary of the available task types that be used in a workflow template:
Content Type Task: Assign a task to a user to create a new content node - task definition allows you to select from available content types.
This module provides a views display plugin to show tasks in a GANTT Chart
uses the libraries API. Please upload the dhtmlx GANTT library
and put it in you libraries folder if you want to use this module.
1. Download and unpack the Libraries module directory in your modules folder (this will usually be "sites/all/modules/").
2. Download and unpack the Views module directory in your modules folder (this will usually be "sites/all/modules/").
3. Download and unpack the Views Gantt (this) module directory in your modules folder (this will usually be "sites/all/modules/").
4. Download and unpack the dhtmlx GANTT js library in "sites/all/libraries".
Make sure the path to the plugin files becomes:
5. Go to "Administer" -> "Modules" and enable the Views Gantt module.
6. Create view with Gantt style and set all required options in the settings.
The Zendesk remote authentication module allows you integrate the Zendesk support service with your Drupal site and synchronize drupal users with zendesk.
Word of Warning: Don't use this module without testing in a sandbox, or a fresh zendesk install so you don't lose data. While this module does work, the module needs testing and testers!
What is it for?
The purpose of remote authentication is so that users that are logged in on your Drupal site are automatically logged in the zendesk support site. User id, name and email will be synchronized between your Drupal site and Zendesk. Drupal becomes the authority for Zendesk logins.
Role based authentication
The zendesk remote authentication module also contains a role based system for authenticating. According to the user roles, the user will be authenticated.
Account syncrhonization allows to have better e-mail support integration. New drupal users are automatically added to zendesk. There is support for editing and updating your users.
After enabling the module, go the the module setting page or follow the included Readme file.
Generally, this project enables content authors to see from any current content (entity) its dependent entities content.
Project overcome a major content control difficulty for content authors.
Provide content authors ability to track external content which refers to current content, without the need to check mass of external content to find out whether each external content refers to current content or not.
Content dependency main advantages:
Easily manage content dependencies - you can view/update for each content entity it's dependent entities from one places.
Backward Compatibility - You can install this module & start use it without need to perform any change in your content structure.
Offers a content-type for a simple To do list. It can be used for anything that needs to be done: getting milk at the store, reminding yourself to update a profile, telling your users to vote on a poll by a certain date...
To do items can be assigned to users with permissions. Items can be given an optional status, priority, start date, and deadline. Items nearing their deadline or with a priority level of immediate are shown in the To do list block (requires the installation of the To do block module.) These events can also fire triggers (Actions & Rules support.)
Each user gets a page with lists of the To do items that: (1) are assigned to them, (2) still exist, or (3) that they created. Quite handy to stay on top!
Detects when new releases of Drupal are available and triggers a build on a continuous integration server. This can be used as part of a continuous integration pipeline where upgrades are carried out automatically by the CI server - very useful for promptly responding to security releases like Drupalgeddon, especially when you manage a large network of sites.
This module gives a possibility to assign or remove specific role for users. Any user with permission "Assign roles" may assign or remove roles for other users. Site administrator defines the list of roles that are available for this.
Convenient filter is available on the settings page of this module and you can choose users with its help. If you want filter users by e-mail you must enter full email to get user. If you want filter users by name, you could enter only first letters.
This module provides an entity to do timetracking. This module is part of the ERPAL Distribution to enable timetracking on tasks. Timetracking is done by one-click to the start-stop timetracking button
This project is developed by Bright Solutions. We also offer paid Drupal and ERPAL integration and process consulting