Loading Profile...
I would love a public API for Tracker
I started to ask this as a more specific question, but decided to generalize it. It would be nice to be able to integrate tracker with other processes/tools we are using (or will be soon in some cases). I'm not sure what you have on the docket, so here is my wish list for your perusal:
- email submission of stories -- this would open a lot of options for how to get data into tracker. Something similar to how iwantsandy.com works would be huge. After this step (and probably enabled by it) would be the ability to create a quick-entry quicksilver action, IM/SMS entry, etc so you could just get stuff collected quickly and efficiently.
- scm integration -- It is sometimes very useful, especially when a bug gets rejected, to be able to see exactly what was changed to fix it. Having it directly integrated with svn (ala trac, or git style) would allow this.
- customer support app -- tracker is great during development, but not geared to support bug tracking/submission by the masses during a large public beta. My dream setup would be using something like lighthouseapp.com for users to submit bugs. Then somebody could coordinate the bug/suggestions that collected there, and somehow send the ones that needed development attention directly into tracker so they become part of the normal development cycle. Having to use two different tools will not only dilute velocity in tracker, but will add the risk of things getting dropped forgotten from one side or the other.
I don't think these necessarily need to be things worked on directly by the tracker team. If there were a published API that opened up some of these interfaces, then we could work on some of the integration pieces and could better fit it into our work processes. If Basecamp can be used to support the myriad of applications it has spawned, imagine how much more useful tracker could be integrated into a development work process.
- email submission of stories -- this would open a lot of options for how to get data into tracker. Something similar to how iwantsandy.com works would be huge. After this step (and probably enabled by it) would be the ability to create a quick-entry quicksilver action, IM/SMS entry, etc so you could just get stuff collected quickly and efficiently.
- scm integration -- It is sometimes very useful, especially when a bug gets rejected, to be able to see exactly what was changed to fix it. Having it directly integrated with svn (ala trac, or git style) would allow this.
- customer support app -- tracker is great during development, but not geared to support bug tracking/submission by the masses during a large public beta. My dream setup would be using something like lighthouseapp.com for users to submit bugs. Then somebody could coordinate the bug/suggestions that collected there, and somehow send the ones that needed development attention directly into tracker so they become part of the normal development cycle. Having to use two different tools will not only dilute velocity in tracker, but will add the risk of things getting dropped forgotten from one side or the other.
I don't think these necessarily need to be things worked on directly by the tracker team. If there were a published API that opened up some of these interfaces, then we could work on some of the integration pieces and could better fit it into our work processes. If Basecamp can be used to support the myriad of applications it has spawned, imagine how much more useful tracker could be integrated into a development work process.
6 people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company is working on this idea.
-
Inappropriate?I have to agree. I would love to have a dashboard widget that shows the current iteration's story. Simply exposing some of that json the application pushes around with a public interface would be a great start. -
Inappropriate?A couple thoughts:
1. We settled on using JIRA and Tracker in tandem on a couple projects, so coordination between them would be useful. On one project, we did our iteration planning in one tool (not tracker, but the same function), and then when we started the iteration, we put the stories into JIRA, each as its own task. JIRA provides workflow and commenting that tracker doesn't need. So facilitating this, coordinating IDs, automatically linking things would be nice.
2. We almost always have a Confluence wiki page backing a story or set of stories. People want somewhere to write more, upload lots of images, etc. Tracker has this, but it is more "comfortable" in a wiki, and people are just used to it. Also, often several stories have a shared wiki page, which tracker doesn't handle.
So some sort of automatic linking would be convenient... we just copy and paste URLs from the wiki into Tracker. We never have pasted tracker links into the wiki.
3. Finally, I don't think having a simple RSS feed of the current iteration would hurt. I don't mind keeping tracker up all day in a tab, but I bet some people would dig the RSS feed more.
-
Inappropriate?I want to be able to import lighthouse tickets into tracker. -
Inappropriate?We're working on an API, and should have something out there within a month or so. The first version will be basic, but it should allow you to access and update story information using REST and XML or JSON.
1 person thinks
this is one of the best points
-
-
Inappropriate?The API is still under development, we're hoping to have the first version out within a few weeks.
-
EMPLOYEE
