TeamCity Issue Tracker Upgrade

Hello,

Let us introduce the new issue tracker that TeamCity will soon migrate to from it's current Jira tracker.

(enters JetBrains Tracker (http://jetbrains.net/tracker), still young but ambitious, not yet released product)

The JetBrains Tracker is developed for some time already, and while it is still very young, it is quite powerful at the same time. As our own (JetBrains) dog food is the food we really like, TeamCity is switching to JetBrains Tracker as our main (and only) issue tracker.

We do understand that in some aspects the Tracker is still a teenager comparing to the elderly Jira, but we believe it has a prominent future and are already impressed by the current features and potential.

We hope that you also will be enjoying the upgraded tracker and you will find it convenient to work with TeamCity issues using it.

The migration is a matter of days. When it's done you will be automatically redirected from the Jira issues to the Tracker ones and TeamCity Jira space will no longer be available. Existing issues IDs are preserved, all Jira account credentials are valid for the Tracker.

Stay tuned for a small quick start guide.

Please let us know if you have any difficulties using the Tracker.

As usual, your feedback is highly appreciated.

Happy tracking,
The JetBrains TeamCity Team

6 comments

very cool... is it going to be as expensive as jira? :)

we use sub-tasks quite a bit in jira... we also like the charting plugin, it provides some nice progress reports in graphical form.

I could really see switching to this product if the price is right...

I've been dying for some ajax action in jira for a while now.

0

Outstanding, particularly if IDEA and TeamCity integration is in plan. In celebration, I'll be the first external user to put in a feature request!

One thing I've always wanted in JIRA is the ability to mark an issue as "blocked" by another issue. When the blocker is completed, the block is removed and the assignee of the blocked issue is notified (along with their manager, optionally). This is a different semantics from the "subissue" construct in JIRA, although obviously related.

--Dave Griffith

0

DG> In celebration, I'll be the first external user to put in a
DG> feature request!
DG>

Since the ice has been broken...

I'd like to see the status of a duplicate item being linked to the status
of the issue it duplicates, as opposed to having it marked as fixed. I'm
constantly annoyed by having to start watching new items (or to traverse
the links every time I need to see what's happening) just because the one
I reported (or have a link to) gets "obsoleted" this way. If the duplicates
could be "merged" somehow (so as to have all the comments and details in
the target issue and have everything pointing there, like older links, notifications,
etc.), even better.

I hope JetBrains can straighten up the thinking here... :)

Best,
Andrei


0

Congratulations, it looks nice so far!

Still I wonder how such a "fresh" product will be able to catch up feature-wise and finally compete against dinosaurs like JIRA, given there's no real distinctive feature (yet!) and not everybody will be willing to migrate all his data to a new system just for the sake of having a fancier UI. But that's just my personal opinion :)

0

awesome!!!


Yegor Yarko (JetBrains) wrote:

Hello,

Let me introduce the new issue tracker that TeamCity will soon migrate to from it's current Jira tracker.

(enters JetBrains Tracker (http://jetbrains.net/tracker), still young but ambitious, not yet released product)

The JetBrains Tracker is developed for some time already, and while it is still very young, it is quite powerful at the same time. As our own (JetBrains) dog food is the food we really like, TeamCity is switching to JetBrains Tracker as our main (and only) issue tracker.

We do understand that in some aspects the Tracker is still a teenager comparing to the elderly Jira, but we believe it has a prominent future and are already impressed by the current features and potential.

We hope that you also will be enjoying the upgraded tracker and you will find it convenient to work with TeamCity issues using it.

The migration is a matter of days. When it's done you will be automatically redirected from the Jira issues to the Tracker ones and TeamCity Jira space will no longer be available. Existing issues IDs are preserved, all Jira account credentials are valid for the Tracker.

Stay tuned for a small quick start guide.

Please let us know if you have any difficulties using the Tracker.

As usual, your feedback is highly appreciated.

Happy tracking,
The JetBrains TeamCity Team

0

Yeah, I was wondering about how they were planning on getting differentiation in this space as well. My hope is that it will be where JetBrains has always excelled at providing differentiation, by providing aggressively developer-centric solutions. JIRA is just fine, but there's not much to it that would tell you that it's for software development, as opposed to any other complex project. IDE integration is an obvious thought (consider in-IDE issue browsing/changelist creation/automatically appending fixed issues with changelists or patches), but I'm not sure that's enough. Possibly build-server integration as well (have TeamCity show not just changed files, but fixed issues)? Release management functionality? Code review workflows? Tight integration with version-control systems (much closer than 'this checkin fixes this issue').

--Dave Griffith

0

Please sign in to leave a comment.