Storm (project management application)
Storm is a project management application for Drupal.
It consists of a set of modules as follows: Storm (base module), Attributes (settings), Organizations, Projects, Tasks, Tickets, Timetrackings, People, Notes, Knowledgebase, Invoices, Invoice items, and Expenses.
Each of these provides permissions to control the sharing of data with other users and organizations, and link together - for example, an invoice can be associated with an organization and project.
All components (except Attributes) are nodes, so can be extended as follows:
- CCK can be used to add more fields to the Storm content types
- Views can build customised views
- Taxonomy (core) can be used to tag the contents of the Storm nodes
- Upload (core) can be used to attach files to Storm nodes
- Comments (core) can be used to permit comments on each of the Storm nodes
CONTENTS:
- Details of modules included in Storm package
- FAQs
DETAILS OF MODULES INCLUDED IN STORM PACKAGE
Storm (base module)
This module is required for all Storm installations provides a Storm dashboard which gives quick links for the other Storm modules as well as to the Storm administration section.
Storm Knowledgebase
Relying only on the Storm base module, this module provides a content type that can be used to collect together important pieces of knowledge, tips and tricks, and can also categorise them by topic.
Storm Attribute
Attributes are the values that are used within Storm, such as task status, countries, currencies etc. This module only relies on the Storm base module, but is needed by all of the following modules.
Storm Organization
This module allows you to create nodes relating to the organizations that are the stakeholders of your projects. If you wish to create invoices using Storm, your own organization should be created as an organization here.
Storm People
Storm People allows the creation of individual contacts within Organizations, and linking of these to Drupal user accounts.
Storm Teammember
This module allows the building of team working on a specific project / task / ticket.
Storm Project
Storm project allows creation of projects attached to organizations.
Storm Task
Storm tasks are the parts that compose a project and can be hierarchically nested to build a work breakdown structure.
Storm Ticket
Storm tickets can be used to track bugs, feature requests, or any other category as specified via attributes. They can be associated with an organization, project or task.
Storm Timetracking
This module allows the recording of time spent relating to particular organizations, projects, tasks or tickets.
Storm Note
This module allows notes to be attached to organizations, projects or tasks.
Storm Invoice
Within Storm Invoice, you can create invoices between yourself and clients. A printer friendly version comes included, and with the addition of the tcpdf library (see the INSTALL.txt), you can also download pdf versions of your invoices directly from Storm.
Storm Invoice Item
As an addition to Storm Invoice, this module allows itemisation of Storm Invoices.
Storm Expense
Storm Expense allows the recording of expenses attached to a specific task or project, including information such as whether it is billable.
FAQs
How themeable is Storm?
Storm is fully themeable - all output is defined by a theming function which can be overriden in your template.php file.
Operation
STORM adds links to the admin menu:
- My account
- Storm
- Attributes
- Invoices
- Organizations
- Projects
- Tasks
- Tickets
- Timetrackings
- Create content
- Administer
- Log out
Create entry
When you list projects, tasks, etc, there is a plus sign in the top right corner of the list heading. Select the plus sign to create a new item.
Most of the items are nodes and you can create them in Create content by selecting the relevant node type. You can also create entries from their parent.
When you view an organization, you can create a project or other entry for the organization by selecting a plus sign from the list to the right of the page.
Create organization
You can create an organization as a customer or a provider or both. You can only create a project for a customer.
Create project
Projects have a parent organization and a title. Everything else is optional.
You can categorize them by Category, Status, and Priority. Plan the project by Date begin, Date end, Duration unit, and Duration. Cost the project using Price mode, Price, and Price currency. Express your artistic self by adding an imaginative Description.
The result is a node and the node creation page lets you select the usual input types, including filtered HTML and full HTML. When you have other node related options and modules switched on, you may have additional options in the creation page.

How to track time
I would like to see more documentation on how to track time. you can add time to tasks and you can create separate time tracking entries. The reports seem to report only time tracking entries. Why would you add times to tasks if you cannot report them? From a beginners point of view, it would be nice to know where to put estimates and how to record time so we can compare estimates to actual.
There is also an experimental Gantt chart thing. What times are used there? How do I record times so I can chart completed against allocated and prevent the assignment of individual developers to more than 168 hours per week?
Time recording and reporting is worth a whole page by itself.
petermoulding.com/web_architect
How to make selected projects public
Is there a way to make selected projects public - visible to all, including anonymous users, while others available only to those who are part of the project?
I have a few open source projects, which I would like to make publicly visible and available for all and I also work on a few contracted projects which can't be publicly available. I can't find a way to set a specific visibility permission on per project basis.
Any input would be very much appreciated.
Artur
Ticket fields
Storm looks really great, I am going to replace Trac which I currently use with Storm, but I would like to customize it a bit. Is there any guide how to customize it?
Is there a way to modify ticket fields?
At least how to:
1. Change default category option
2. Change status values (and default value)
3. As I want to use it for an open source and public projects I would like to remove Price fields, or at least make them invisible for some users....
I found something...
Looks like most of this can be modified in the stormattribute table where all such attributes are stored. I guess there is not web interface yet for managing these attributes?
Views?
Storm works with Views and cooperates with CCK. Under D7, Fields will be in core, replacing the CCK functions, and CCK will be the admin interface for Fields. Storm D7 will most likely use Fields. If you want some sort of extra lists and interface, you could develop using Views then submit them to the Storm project. By the sound of your requirement, you could also need additional permissions.
petermoulding.com/web_architect
Could I please encourage you
Could I please encourage you to use the issues queue at http://drupal.org/project/issues/storm .
@peterx has given you good answers here, but the issues queue is the central hub for support.
Magnity
http://webdesign.magnity.co.uk
Drupal 6 themes | Drupal 6 Storm Demo | Drupal 6 Casetracker D