Loading Profile...
Questions on Bug Tracking in PT
Some of the teams at work are excited to find a tool as great as Pivotal Tracker, but there are a couple of things we can't figure out, and we are hoping someone can point us in the right direction.
First - is there an easy way to tie bugs to particular stories, other than manually cross-linking them? It would be brilliant if there was a "File bug" button on stories that would file a but against the story and cross like them automatically. Better yet would be if the bug link was struck through on the bugged story when the bug fix was delivered and accepted. Failing a feature like that that we are not seeing, are there any suggestions for third party issue tracking systems that integrate well with PT? Our QA team just wants a little more functionality in filing bugs.
Second - Can we move bugs between projects? The server and client teams have independent development schedules and separate PT projects, but often when a root cause is tracked on an issue it's found that it's filed against the wrong team (a client bug logged against the server ,or vice versa). If there's a way to toss bugs over the wall to the other team's project, or bat them back and forth as they are being investigated, we would love love love to know about it.
Those are our two big ? at the moment. In general we like PT a lot, and we're eager to get more use out of it!
First - is there an easy way to tie bugs to particular stories, other than manually cross-linking them? It would be brilliant if there was a "File bug" button on stories that would file a but against the story and cross like them automatically. Better yet would be if the bug link was struck through on the bugged story when the bug fix was delivered and accepted. Failing a feature like that that we are not seeing, are there any suggestions for third party issue tracking systems that integrate well with PT? Our QA team just wants a little more functionality in filing bugs.
Second - Can we move bugs between projects? The server and client teams have independent development schedules and separate PT projects, but often when a root cause is tracked on an issue it's found that it's filed against the wrong team (a client bug logged against the server ,or vice versa). If there's a way to toss bugs over the wall to the other team's project, or bat them back and forth as they are being investigated, we would love love love to know about it.
Those are our two big ? at the moment. In general we like PT a lot, and we're eager to get more use out of it!
I’m concerned
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi Ian, glad your teams have discovered Tracker!
The tool's primary purpose in life is to enable teams to collaborate around a prioritized backlog, rather than to support issue triage and organization. As such, feature support for the latter is fairly minimal. Nevertheless, these are fairly common questions/requests on large projects, especially when the product is already in production, and we're actually about to start work on some integration features, which would allow you to connect Tracker to a bug-tracking application and keep stories in sync. We hope to have the first version of this available within a month or so, at least for some bug tools.
Moving stories between projects is also something we'd like to tackle soon as well, but we have fairly limited bandwidth at the moment. In the meantime, one way to accomplish this is to export selected stories to CSV, and import them to another project.
Hope this helps... -
Inappropriate?Dan,
Thanks for the quick response, the integration work is exciting news. Do you have any information about which systems are first in line for integration?
I’m optimistic
-
Inappropriate?Not exactly, but Lighthouse, Trac, and JIRA will probably be some of the first few. The approach we're going to take, though, is to extend the API so that anyone can write a bug tool "connector". We'll probably write a few ourselves, to serve as examples, but hopefully the user community will be able to help!
1 person says
this answers the question
EMPLOYEE
