Authorization

As you, all knew we shifted from Trac to Redmine for project management (issue/ticket tracking, source control management, mileposts). I am egger to tell few revealing facts experience at Redmine comparatively to th at of Trac setup my previous location.
I have concluded from the Trac mailing list and further discussion on the comments by some core developer is that the prime objective of Trac is to generate or build a basic static or groundling an extendable with the use of plug-in, which is a supreme mission statement. It poses but in it, as if once you are managing numerous Trac installations at a time, this scope turn out to be against you in an agile manner, though I miss few important things in Trac.
MULTIPLE PROJECTS
The initial ground for moving to Redmine was of the lacking sustained for multiple projects at Trac. I am sure you can hack Trac (see track- hacks) to let in multi project support, but still I do not prefer hacking. There were various discussion how (and if) Trac should enforce multi-project support concept: there lies no “out-of-the-box” resolution. I study something about Trac v2.0 supporting this, so I may suppose we will find that in around 2015 or so.
Whereas best thing about Redmine is, it does affirm multiple projects. The desegregation throughout the entire system is top-drawer. It allows you to create nuzzled subprojects and move issues/tickets from one to another project. Even for each project, one is free to assign different users and turn a few functionality (milestones, source control, time tracking) on and off which is additional icing to the sugar.

BATCH ISSUE/TICKET EDITING
I have to agree Trac ticketing system is very powerful and flexible. Without a doubt Trac is one of the most common and stable tools for online project management & issue tracking for a very good reason. You can easily search and filter tickets by severity, project component, version or owner, and then store those. Great.

What i really miss using Trac is the ability to do a “mass update” (edit/close/move) on several tickets at the same time. This is where the ajax powered “batch edit” feature of Redmine comes in quite handy.

USER / ROLE MANAGEMENT
The user management in Redmine is great ! Besides normal user management it supports (custom) roles. You are able to set different user roles for different projects.
Trac doesn’t support “user management” out-of-the-box. Unlike other bug-tracking systems that simply have a table for storing the users, Trac took the approach of allowing users to leverage the numerous authentication modules available for their web server. This means system administrators are able to hook Trac into something like LDAP, Active Directory, or whatever centralized user system that they already have in place.
So which one is better? Difficult question. I am a great supporter of working software out of the box. Not too much configuration, easy to install. This doesn’t mean the software has to be “simple” : flexible and easy-to-configure can go along hand in hand. That being said i think Redmine took the best approach in having good user management right after installation. If you need something more centralized they still have LDAP support.
Few Additional Features
Well, its certain Trac is much more stable than that of Redmine. Therefore, if you necessitate a stable product, Trac is better. However, as far as a minor web design company like ours is concern, the stability of the maturation environment is not actually that decisive to us.
Now what we aspire for in, online project management software is innovative features/plans to improve the way our squad is operating together. I frequently monitor the Red mine timeline / activity to observe how other people are utilizing the Redmine platform. Though many of their reviews/ideas inspire us to alter the way we are functioning or initiate applying a particular feature yet we have not paid enough attention.
Shall we see for more?
However, every coin has two sides similar is the case with Trac. Trace has a vast community with a multiple core developers, while in Redmine has a restricted access build around with few person involved. The source repository browser in Trac is comparatively more herculean and visceral.
Now since I am working along Trac for a long time and hence posses a great deal of regard for the hard work of all the people associated on projects.
Still as discussed earlier the Trac strength is also its impuissance somewhere. The key is to maintain the system less accented as it can be, other prime features does not sound worth for core decision making at the end.
[via www.digitalbase.eu]
Comments (39)
RSS Collapse / Expandcustom stickers
muqtada123
Scott Allerdice
Software Engineer
android application development
scottallerdice
blogging for dummies
jcbrown
inter4522
Meridian
zara454
QuickHomeSale
seoaddiction
JohnsonSmith
glucomt
glucomt
spsdel99
Fast Payday Loans
superwork
instant cash
jennypaul123
Bad credit payday loans direct lenders online
andytaylor023
nabihahayat
Affiliate Marketing Tips
Instant Payday Loan
alianasmith11
alanf
-traders insurance
davesteve12
superwork
superwork
I almost convinced my bosses to use Redmine yeasterday in a presentation:)
The topic was on the table with him was exactly these private matters.
The patch proposed by Jeffrey Jones is the internal / external users.
I'm asking now for the skill on the issue of reporting to be private to the user who reported it. Must have a permit for this feature — other topics View private.
Redmine is a great innovative tool, and we use it as a project management solution, through the publication of the work not just developers, but the work of project managers. It adapts to our organization, but for now, the lowest levels of the hierarchy should not see the higher-level work.
madihaghafoor
superwork
liajames123
hermans25
HelenOlsson
seoweb2
TomSmith1
piternoize
step in writing eassy service
carriepena
term papers on war
ritasummer79
how to write Essay Writing
jacobhubbard88
Only Registered and authorized users may post comments