The workflow module allows the creation and assignment of arbitrary workflows to Drupal node types. Workflows are made up of workflow states. For example, a workflow with the states Draft, Review, and Published could be assigned to the Story node type.
Case Tracker enables teams to track outstanding cases which need resolution. This module was inspired by the issue handling in project module, but unlike Project module, which is specific to software development, Case Tracker was designed to be a generic issue tracker.
Case Tracker is usable right out of the box as a basic ticketing system, it's default UI is minimal but feature complete. The module was designed to be extended by programmers and site builders to meet complex needs, and so tries to avoid making too many assumptions about all the ways it can be used.
Case Tracker is not the only ticketing system in Drupal. This comparison may be useful when choosing a ticketing module.
Actually, the 7.x-1.x-dev version has the content types for Project and Cases working without problems. The Notifications, Actions and View integration that needs to be tested.
The development is active and we're working toward a release. Check out the 7.x-1.x branch and post your patches!
Drupal 6 version is fully featured and stable, and you can use without problems
These are the main Features of the Open Atrium distribution. There are 6 core features available by default when you install Open Atrium:
- Atrium Blog - Provides a method of sharing stories and information with other members of the group
- Atrium Notebook - Provides a method of building organized documentation within a group
- Atrium Calendar - Adds a group calendar, with the ability to add collective events
- Atrium Case Tracker - Adds the ability to manage and track issues, assign them to members, and discuss them.
- Atrium Shoutbox - Provides a rapid discussion board for short discussion or comments
- Spaces Dashboard - Adds a configurable dashboard to a group home page in order to easily review new or updated information.
Read more documentation about these Features at https://community.openatrium.com/documentation-en/
The Maestro module is a workflow engine/solution that will facilitate simple and complex business process automation.
Maestro has a number of components that include the workflow engine and the visual workflow editor. The workflow editor is used to define the workflow, creating a workflow template. 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. New task types can be developed and added much like the Drupal CCK module can support new field types. Initially we will have the following task types:
- 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.
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!
For more information, read the extensive documentation.
This module provides a way to maintain the size of your backups under control.
Backing up with Backup and Migrate is great, but it can build up a huge amount of data rapidly.
Backup and Migrate Prune aims to solve this problem. The approach taken is simple.
- For backups made today: Keep all backups.
- For backups made this week: Keep one backup per day.
- For backups made this month: Keep one backup per week.
- For backups made this year: Keep one backup per month.
- For older backups: Keep one backup per year.
The module is configurable to allow some customizations to this. For instance you can stop pruning at level 4 and leave a backup per month for older years.
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.
You know Storm? A great project management suite based on Drupal. If there was a downside it's the fact that it's all good old html and navigation is therefore a bit outdated. This is now history: Storm Dashboard is a very powerful yet simple to use dashboard which needs just one pageload and everything else is done dynamically by using JQuery.
It's all themeable and it does not require any configuration. Just download it, install it and have fun dahsboarding - dynamically!
- The 6.x-1.x Branch is stable and works great with the Storm 6.x-1.x Branch
- The 6.x-2.x Branch is in minimaly development and open for new features and is the recommended Branch for Storm 6.x-2.x Branch.
- A 7.x branch is not planned. Please consider using ERPAL instead.
BugHerd is an issue tracking system built for desginers 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 in the admin area.
This module was written by Dave Hall in around an hour. The module was backported to Drupal 6 by RealityLoop.
Storm Contrib is an add-on to the Storm project.
It offers extensions and new features to the Storm modules to improve projectmanagement for small and middle companies.
Finally we are in the beta phase! Please help us test all the modules!
Your feedback is most welcome! So please don't hesitate to contact us or create issues.
- extends the core Storm content types
- more projectmanagement features like balances, progress, project schedules
- cost calculations
- project balances based on project budgets
- conversion and calculation of different currencies
- single-page overview of a project's tasks and tickets (project schedule)
- utilisation of persons (how much each person is working or available)
- consideration of weekends and national holidays
- consideration of holidays by individual people
- Apache Solr Search extension to search just Storm content types
- ticket dependencies
- timetracking lists for each person per day
- timetracking statistics for each person per day and per month
- timetracking favorites list for each user - easy start and stop of timetracking, without many clicks
- exports lists as .csv, .xls, .doc
- option to save filter settings for each user (finished)
- and much more ...
The Architecture module provides reports documenting how your Drupal site is architected.
Currently it provides three reports:
- "Site Entities" lists all content types, taxonomies, and other Drupal entities that have been defined for your website. Entities that are fieldable also include a list of all fields for that entity.
- "Site Taxonomies" lists all taxonomies and their associated terms.
- "Site Variables" lists all variables and their values.
These reports are not intended to provide an administrative interface for editing or configuring your website. The purpose of this module is to provide some easy-to-read documentation of how your site is put together. The reports are designed so they can be viewed online but also easily copied-and-pasted into word processing documents for sharing information with people who don't need to see a lot of technical detail or specialized Drupal terminology. (I created this module so I could create some reports for discussing site design with clients and sharing specifications with other developers.)
Other functionality that I might want to include in the future includes:
- A list of enabled modules (something simpler than the admin/modules page).
Includes multiple modules for video communications including room listing, pay per view access control:
- Video Conference integration
- Video Chat integration
- Video Consultation integration
- Live Streaming integration
- Room List
These modules allow setup of Pay Per Minute / Pay Per View ( PPM / PPV ) video chat, consultations & e-learning, webcam live shows, conferences using VideoWhisper Drupal Modules.
See project Resources > Home Page : VideoWhisper Drupal PPV Video Streaming Suite, to read more about this project, installation instructions, requirements and configuration.
Before installing, make sure your hosting environment meets all requirements. These web based video communication applications have demands beyond regular Drupal requirements: a compatible rtmp host is required for live interactions and video streaming.
Site Memos is a very simple administration module that encourages you to
record information about your site in a permanent record that can be easily
accessed and edited by you, your team, and others who may follow you.
Site Memos does not create any memos - you have to do that yourself. It also
does not impose any structure on the memos you create. It is really just a
flag that you and your team can always find to allow you to maintain your own
Memos you may want to record could include:
- Rationales about module and theme choices and configurations
- Plans, schedules, and To-dos
- External info - servers, Varnish, CDNs, etc.
- Contact info
- Recognition for key people
Site Memos is easy to install and configure.
It is used by administrators or developers, not site visitors.
Records all cookies that all users have set when they load a page.
This allows easier auditing of cookies on your websites for conformance with the EU cookie law.
Information appears under admin/reports/cookies
A collection of preconfigured Views to add to the dashboard of your Open Atrium groups.
- Book pages (with "Add Book page" link)
- Member Listing (including admin vs. user status)
- Projects (Case Tracker or Case Tracker Plus)
Additional submissions are welcomed.
- Visit /admin/build/features on your site to enable this Feature.
- Visit /admin/settings/dashboard on your site, select the "Dashboard Views" section, and enable this module's blocks.
Drupal 7 version information:
The database is backwards compatible with the Drupal 6 one. Just drop the module into your D7 upgrade installation and enable it; it should start working right away.
Drupal 6 version information:
The Drupal 6 version of this module is in maintenance only mode. No new features will be added.
The Harvest module allows you to integrate Harvest Time Tracking (http://www.getharvest.com) with Drupal. Using the Harvest REST API this module will connect to Harvest to allow you to display and use information from Harvest.
Typical Use Cases
- Create customized reports to display Harvest project data and share with team members and/or clients
- Keep your clients up to date on how many hours your team has spent on their project and on what tasks
- Remind your project team with regular updates on the project budget status
- Automatically generate time reports for contractors to add to their invoices
Harvest Projects Module
Atrium Scrum is a collection of features to help implement a robust Scrum process on Open Atrium.
- Atrium Scrum: User Stories: Provides a content-type structured around the proven "As a <role>, I want to <feature request>, so that I can <goal>" agile pattern.
- Atrium Scrum: Tasks: Exposes a task board to efficiently organize the team's efforts toward completing a Sprint's User Stories and their associated Tasks.
- Atrium Scrum: Backlog: Provides an intuitive drag-and-drop UI for maintaining a Product Backlog, keeping it prioritized, and assigning User Stories to Sprints.
Time entry is an entity type for storing time intervals.
The Storm Knowledge Base module provides a simple way of managing knowledge as part of the Storm set of modules.
Since January 2012, Storm Knowledge Base has been maintained as a separate project.
You only need to download this project if you are using Storm 6.x-2.x onwards.
Simple timeclock or time management module. Punch in under a project code, clock out with a short description of what you did - creates a node called a shift which you can later edit. Two basic views included, one that shows a list of everyone logged in - the other a list of all recent shifts, with exposed filters for project code, employee first and last names, and start and end times.
Two blocks are also included - one that allows the punch in/punch out, the other a view of everyone punched in. Two Roles also included - Employee and Supervisor.
This time clock is a distributed as a feature but has some additional code in the .module for the punch in/punch out block.
In just one tiny function, this module does nothing but provide a category named "Project administration" in the admin overview. Other modules can depend on this one instead of creating their 'admin/project' menu paths all by themselves.
This module makes sense because there is no single project management related module that all project management related sites use, and without this module, other ones must either duplicate the 'admin/project' menu path with special care, or put themselves into 'admin/settings' in order to avoid complications. By depending on this module however, other modules can simply register 'admin/project/*' menu paths and be done with it.
This module provides a bridge between Domain module and Workflow module. It makes it possible to have a multisite setup with Domain module and also maintain a consistent and working publication workflow.
Makes it possible to alter (change values of) fields on a node when leaving a comment.
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.
Software Projects is a bundle of configuration that adds issue tracking features to an Open Atrium project. Open Atrium comes with an issue tracking system that is based on the Case Tracker module while OG Software Projects is based on the "Project" modules.
The 2.x branch will be a complete rewrite (by hand, for the most part).
My vision for this module is the glue and extra parts required to create a system like Unfuddle. I will be using Open Atrium, primarily, but I would like to build the module in such a way that it will work on any Drupal site.
When all of the following features are complete, a 2.0 release will be rolled:
- Include a repo viewer
- Provide an easy interface for repository management (like Unfuddle)
- TODO: Others?
If you'd like to see the 2.x branch completed soon, please contribute!
Developed by cweagans
What is this?
Case Tracker Commits integrate Version Control API with Case Tracker
intercepting the commit messages parsed by Version Control and matching some
patterns that identify a relation with a case ID.
The current pattern we use is: ref [case_nid] text_message
Provides some blocks that could be added in the Case Tracker Nodes that list
all the commits of the case. This is handled via Views and could be configured
all the fields that you want to show in that block.
How it works
Version Control API Git integrate repositories with Drupal in the configuration
of VCS Repositories. This configuration tells Drupal to track all the changes
that happen in that repositories this task is delegated to Drush command
"vcapi-parse-logs" this task get all the logs executing the command git log via
git binary and retrieves all the commit information that is stored in database
Note: the Git repositories must be in the same server where the Drupal instance
that will execute "vcapi-parse-logs".
In the process of parse logs each entry call a
hook_versioncontrol_entity_commit_insert passing the operation information.
Case Tracker Commits implement that hook and use it to parse the message to
search a case_nid pattern that permit relate operation with case.