To finish our recent round of Search updates, you can now refine searches, using AND, OR, a minus sign to exclude items, and use combinations of all search options in Tracker.
Full details of all the ways you can search are in the FAQ, but here are a few examples:
Want to find everything with one label or another that haven’t yet been started?
Read more »
We’ve been continuing work to bring you a few more of the Search options you’ve been asking for. As well as a few fixes, we’ve extended the ability to search on created:, updated:, accepted:using before/on/after criteria, e.g. created_before: 11/19/2012 specifying a date range, e.g.
Read more »
If you’ve been seeing a lot of “Aw, Snap!” crashes while using Tracker in Chrome, you’re not alone. An issue seems to have been introduced in Chrome 28 and several web apps and sites have been affected by it.
We’ve reported the problem to Google, (and they merged our report into this issue) but since they haven’t been able to fix it yet, the best way we can think of to assist them, is to ask your help.
Read more »
Pivotal Tracker lets you stay on top of everything to do with your project, but sometimes your stories need a little something extra.
Fortunately when some of our customers feel that way, they share the results. Here’s a roundup of recent test related Third Party Tools to help you make the most of your bugs in Tracker.
Read more »
There are times when you might want to invite someone to your project but only give them read-only privileges in it. You might also want to change an existing project member’s access so they can see your project but not add stories or make changes to it. Also, read-only project members don’t count against plan collaborator limits for an account.
In such situations, the Viewer role in Tracker is just what you need.
We recently launched epics, to make it easier to plan and track progress of large features at a high level. Whether you are in the early stages of defining your product or have a Pivotal Tracker project you are working in already, epics can help you manage your work more effectively. In this article, we’ll show how to create epics, for a hypothetical shopping site project.
Bugzilla is a popular Tracker integration and fairly straightforward to set up. In general all you need is here: https://www.pivotaltracker.com/help/integrations?version=v3#bugzilla
But if you do receive an error message instead of bugs loading in your Bugzilla integration panel, here are some tips to get past them. The following also applies to other error messages, but these are the most common:
"Unable to load bugs - Please check your URL and remember to include http:// and exclude the xmlrpc.cgi."
"Unable to load bugs - There was a problem processing your request."
You can take the first error literally, but there are also some other causes for it which aren't obvious.
We only support versions 3.4.x and above. That said, at the time of writing, we're looking into an issue with the the 4.2.0 release and possibly some preceding minor versions and release candidates.
If you haven't changed the integration's "Bug 'Status' values to exclude" (currently RESOLVED, VERIFIED, CLOSED), these defaults could be trying to pull in too much data and hence failing. To check, log in to your Bugzilla instance and use the advanced search options to find a small number of bugs, to help you change the default values to exclude all but those, and see if they'll be pulled in.
You may need to install one or more optional Perl modules, i.e. SOAP-Lite and possibly Test-Taint. To determine if you have them installed (or to get the commands necessary to install them), go to the directory where you installed Bugzilla on your server and run the checksetup.pl script. It will tell you what modules are installed, and what optional modules can be installed (and what they will enable). Check to see if these modules are there and if not, install them.
Once that's done, you can test it using the following. To run this you'll need access to a machine that has the CURL command. Create a file called version.xml with the following text:
<?xml version="1.0" encoding="UTF-8"?>
Then run this curl command:
curl -X POST -H"Content-Type: text/xml" -d @version.xml <url of Bugzilla server your>/xmlrpc.cgi </url>
To see a successful version request, run the command against the Bugzilla "Landfill" test server. For example:
curl -X POST -H"Content-Type: text/xml" -d @version.xml https://landfill.bugzilla.org/bugzilla-4.0-branch/xmlrpc.cgi
If all is well, the response should look like this:
<?xml version="1.0" encoding="UTF-8"?><methodresponse><params><param /><value><struct><member><name>version</name><value><string>4.0.2</string></value></member></struct></value></param></params></methodresponse>
If the response printed by the curl command accessing your Bugzilla server is like this, then the Tracker integration should be able to access your Bugzilla server. If this is not the kind of response you get, then your server is still not setup correctly. In general the response's content should help you troubleshoot. For example, if contains, "The XML-RPC Interface feature is not available in this Bugzilla." it means you need to enable the XMLRPC interface on your Bugzilla server.
However, if you are using version 4.0.5, a bad response (such as "Application failed during request deserialization: 32612: When using XML-RPC, you cannot send data as text/xml; charset=utf-8. Only text/xml and application/xml are allowed.") could be the result of the following Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=731219 It's been fixed in the patch referenced in the bug, but by the time you read this, there may be more recent updates.
Another problem can be with the data that is being transferred to Tracker, if there are one or more bugs which contain multibyte characters in the description or comments. This is usually a result of pasting text into a bug from rich text email or office documents. These characters cause the length of the data stream that the web server sends to us to be incorrect, and we are unable to parse the XML on our side. In that case, determining if your bugs have any multi-byte characters and removing them, should resolve the problem. We can provide steps to help you with this if you need them.
The above should cover the most common problems. Hope it helps.
Finally, we get asked if you can integrate Tracker with Bugzilla if it's behind your firewall. Yes, we have 2 API servers that you can allow through your firewalls for Pivotal Tracker integration with your Bugzilla server, "api.pivotaltracker.com" and "api2.pivotaltracker.com". Please refer to our Integrations help page for more information: http://www.pivotaltracker.com/help/integrations
If you have any questions, or there's something this doesn't cover, please send email to: firstname.lastname@example.org