Moving to JIRA
Moving to JIRA
Posted over 2 years ago by romanb
While we really like Trac, especially its subversion integration, it has a lot of shortcomings for bigger projects in the area of project & issue/ticket management. Hence we decided to evaluate alternatives and ended up with choosing JIRA. Its normally not free software but the generous guys from Atlassian granted us a free open source license. A big thanks from all of us to Atlassian for their support of open source projects.
From now on all the project management, release management and issue/ticket management will happen in our new JIRA instance. While it is open for everyone in read-only mode, we strongly encourage you to create an account soon so that you can create/modify/comment issues and content in JIRA.
Trac is from now on closed for tickets. All new tickets need to be reported through JIRA. We are not going to automatically import all tickets from Trac to JIRA because that does not work very well and would require to import all user accounts as well, which can not be done easily either. We will continue to work on the "old" tickets, always starting with porting a ticket over to JIRA before working on it. If you want to help, you recreate tickets that are especially important to you in JIRA yourself. You can still log in to Trac and view tickets for the purpose of migrating them to JIRA but you can not modify them or create new ones.
When you recreate an issue in JIRA, please make sure you close the issue in Trac with the resolution: "migrated".
Trac will not be completely shut down, however. The following functionality will stay open:
- Wiki
- Timeline
- Browse Source
That is, the wiki and the subversion integration. We basically use Trac as the subversion viewer that we coupled with JIRA. Any changeset numbers or file references in JIRA issues will link to the changesets/sources in Trac.
We're looking forward to working with JIRA and we think it is an improvement for all users. We hope you enjoy all the new functionality provided by JIRA, like voting for issues that are important to you, tracking issues and much more.
So, head over to our JIRA instance, create an account and start creating issues and explore the features.
Comments (14) [ add comment ]
Captcha bug Posted by phil0 about over 2 years ago.
I can't create a user, the captcha image produces an error (500).
Why JIRA? Posted by jumski about over 2 years ago.
Hi!
I was wondering why you have choosen JIRA over for example Redmine?
What's the difference? Posted by vadik56 about over 2 years ago.
What are the advantages of using JIRA over Trac?
@phil0 Posted by romanb about over 2 years ago.
captcha is disabled for now, you can now sign up. We will reenable the captcha once we know whats wrong with it.
@vadik56 Posted by romanb about over 2 years ago.
There are plenty of advantages. Trac has really nice subversion integration but when it comes to issue tracking and project management there are a lot of shortcomings: No support for multiple projects, multiple subversion repositories (you would need multiple trac instances), very very very few administrative features in general... You likely didnt notice it but we had to do a lot of stuff manually, often through issuing direct SQL to the live database, like moving all remaining tickets of a completed milestone to a new milestone and more.
JIRA has many more features for you (the users), too, which you will hopefully soon see! Especially voting for issues so that they appear in the popular issues, making it visible to us that there is high demand to fix a particular ticket is something most users will welcome I think.
Every user can customize their own dashboard, throwing all the stuff out you dont wanna see and having the things that interest you most right there on the start page and there's a lot more.
@jumski Posted by romanb about over 2 years ago.
No particular reason for choosing JIRA over Redmine, we just had to make a choice at some point and JIRA has already proven to be a good choice for large projects (Zend Framework, Hibernate, ...) and probably because I, personally, am more in the Java camp than in the Ruby camp :-)
Editing an issue Posted by craig about over 2 years ago.
Hi,
JIRA's a welcome improvement. I don't appear to be able to edit an issue after I've submitted it though?
Cheers
@craig Posted by romanb about over 2 years ago.
Might be a permissions issue. I will look into it.
@craig Posted by romanb about over 2 years ago.
Fixed!
@romanb Posted by Jay about over 2 years ago.
While it's difficult to compare JIRA and Trac (JIRA is an expensive commercial project, Trac is a free open-source project), some of the points you've made against trac aren't necessarily valid.
1) Newer versions of Trac "support" multiple projects/multiple repos. We're using it at the company I work at, and it works fine for basic separation, but otherwise features are limited (can't use multiple repos in a single project, can't easily cross-reference other projects from inside another, etc...).
2) Moving all open tickets from a completed milestone to a new one happens automatically in Trac as of version 0.11.1 (perhaps earlier). When you close the milestone through the Web UI, there's a checkbox that allows you to do just that, no custom SQL needed.
Just wanted to set the record straight. :) Good luck on the move.
@Jay Posted by romanb about over 2 years ago.
Thanks, I didnt know that yet, we've used 0.10.4 for too long probably. These were really just examples and when I say "this or that did not work well for us" I am well aware that there are probably solutions to these issues somewhere. So I really didnt want to make any false points against Trac, I just stated some examples of things that caused us problems for a long time! I still like Trac, I am unable to hate/dislike good open source software ;-)
Trac is intended to be minimalistic software and I respect that, it just doesnt work out for us anymore, it is too minimalistic for us in many scenarios.
Thanks for your clarifications!
trac account Posted by adrive about over 2 years ago.
Hi. I have a problem to browse the tickets in trac.
REPORT_VIEW privileges are required to perform this operation
I want to look for tickets i reported, i need the privileges.
@adrive Posted by romanb about over 2 years ago.
Permission granted (to authenticated users, so login first)!
Confluence and Fisheye Posted by Fabian about over 2 years ago.
Doesnt the Atlassian OS Model also cover FishEye and Confluence? At work we use the whole Atlassian toolset and it is a real productivity toolset. Working with trac and JIRA is just incomparable. This is just my oppinion, but I use both tools every day :)