ProcessMaker Bug/Issue Tracker

The ProcessMaker Bug/Issue Tracker is based on MantisBT and is used to report bugs and suggest improvements and new features for ProcessMaker.

Members of the community should report their bugs/issues/suggestions under the "ProcessMaker" and "ProcessMaker - Development Version" projects, which are open to the public. Anyone can read the bugs, but it is necessary to register as a user in MantisBT in order to file a new bug/issue report or add a comment to an existing report.

In addition, clients with support contracts have private projects in the ProcessMaker Bug/Issue Tracker to register their support tickets. Each client will be given a project name, such as "Acme Inc". Only the client and the members of the ProcessMaker support and development have access to these projects. New support clients should receive an email explaining how to access their private projects in MantisBT.

Viewing Bugs/Issues

To view and report bugs/issues/suggestions for ProcessMaker, go to: http://bugs.processmaker.com

To search for an existing bug/issue, click on View Issues in the menu. Enter text in the search box and select any search criteria in the dropdown boxes. Then, click on Apply Filter and a list of reports will appear in the list below.

For example, if searching for a problem in subprocesses, enter "email" in the search box and . Note that the search is case sensitive, so "it will find any bug which includes the words "Email", "eMail", "EMAIL", etc.

To view a bug/issue report, click on its number which links to that report:

As bugs/issues are handled their Status will change:

• New: The report has been filed in the system.
• Acknowledged: The report has been read by a member of the ProcessMaker team.
• Confirmed: It is confirmed that the bug/issue exists by a member of the ProcessMaker team.
• Assigned: The bug has been assigned to a member of the ProcessMaker team to work on it.

Note: Before September 2011, new reports were automatically given a status of "Assigned", so for bugs/issues previously filed, "Assigned" only means that the the report has been filed in the system.

• Feedback: A members of the development or support teams have asked a question and are waiting for a response from the reporter.
• Resolved: A member of the the development or support teams has either fixed the bug, reported a workaround, or decided that the bug won't be fixed. At this point, members of the Quality Assurance team will begin testing the bug and leave comments to also confirm that the bug is "Resolved". If not, they will change its status back to "Assigned".

Note: It can take weeks and even months for bug fixes to be included in the next stable version of ProcessMaker, so don't assume that a "Resolved" bug has been fixed in the current stable version.

• Closed: The bug/issue has been closed, which can mean:
  • The development team decided to not fix the bug or implement the requested feature.
  • A workaround is available in a released stable version of ProcessMaker.
  • The bug/issue has been fixed in a released stable version of ProcessMaker.
  • If a support ticket for a paid client, the issue has been "resolved" and the client has not reported any further issues on the ticket for a certain amount of time.

Reporting New Bugs/Issues

Before reporting a new bug/issue, first search if the bug/issue has already been reported. Once sure that the bug/issue has not already been reported, click on Report Issue to file a new report.

If unsure if the bug is really a bug or if a workaround exists, feel free to ask in the forum, however, it does NO good to report bugs in the forum, since the ProcessMaker developers do not regularly read the forum. Even if a developer does respond in the forum, it does not guarantee that anyone in the development team will be scheduled to work on the bug/issue. The only way to guarantee that the developers will consider the bug/issue is to file a report.

When reporting a bug/issue, first select the project:

If using a stable version of ProcessMaker, then select the "ProcessMaker" project. If using a development release, then select the "ProcessMaker - Development Release" project. If reporting a support ticket as a client, then select the name of your project, such as "Acme Inc.".

Then fill out information about the bug/issue:

When reporting a new bug/issue, please fill out the information as completely as possible. It is very important to include the ProcessMaker version number and the name and version of the operating system of the ProcessMaker server. Please indicate the steps to reproduce the bugs. If relevant, include the name and version number of the web browser client in the Additional Information box.

If asking for a new feature to be implemented in ProcessMaker, select the "Yes" option in the New Feature Request dropdown box. If it will help the ProcessMaker developers understand the problem, please provide a screenshot.

Note: If reporting a bug which produces an error or warning message, please copy the message and paste it into the Additional Information box, so that it is easy to find with a text search. If the message is only included in a screenshot, then it can not be found with text searches.

After clicking on Submit Report, the new bug/issue should appear in the list of registered reports:

To open the bug, click on its link in the list.

Note: Clients with support contracts are generally given priority in the fixing of bugs and implementation of new feature requests.

Commenting on Existing Bugs/Issues

If the bug/issue has already been reported, it may help to add a comment in the following situations:

• To indicate that the bug is affecting you and ask that it be worked on. Comments help developers decide which bugs to work on first.
• To indicate that the bug still exists in a more recent version.
• To indicate that the bug also exists in a different context than what was reported.
• To provide feedback to questions asked by the ProcessMaker support or development teams.

It helps to indicate where the bug was encountered. Depending on the type of bug, it might be appropriate to indicate what version of ProcessMaker, the operating system of the server and the name and version of the web browser. For example:

I also see this problem in version 2.0.31, running PM on CentOS 5.5, using clients with FireFox 3.6 in Windows XP SP2. 

For other types of bugs, it might appropriate to add a comment with the code or the context. For example:

I see the same error message when I run a case with this trigger:
-------
$caseId = @@APPLICATION;  
$result = executeQuery("SELECT * FROM APPLICATION WHERE APP_UID='$case'"); 
-------
I'm using version 2.0.31, installed in CentOS 5.5, using clients with FireFox 3.6 in Windows XP SP2.

Registering in the Bug/Issue Tracker

Only registered users can file bug/issue reports. To register as a new user, go to http://bugs.processmaker.com and click on the Signup for a new account link above the menu bar:

Then, fill out the "Signup" form, entering a username and email address, plus the code in the CAPTCHA image:

When done filling out the form, click on Signup to send in the new account information. A message will appear, confirming that the information has been received. Click on the Proceed link at the bottom:

Then, login to your email account and open the message entitled "[MantisBT] Account Registration". Click on the link in the email to verify the registration at that email address.

Your browser will be redirected to a Mantis screen to edit the registered username and email address and enter the full name of the new user and a password, which needs to be entered twice:

Click on Update User to change the information about the user, and begin using the ProcessMaker Bug/Issue Tracker.