2010/11/18 Michael Wheatland <michael@wheatland.com.au>
I think if we were going this way, the 'case tracker' module would be more
appropriate as the issues module is build into the 'project' module.
Correct
me if I am wrong.
No, you're right, Project Issue module depends on Project module :P But I
don't see that as a problem. Project is designed specially for software
projects, so, there is no problem here :D And the Issue module is the one
used at Drupal.org, so we can rely it will be maintained and that
it's powerful and feature rich enough. I like that case tracker
doesn't assume that the ticketing system will be used for software (like on
a corporation for support tracking) but I think Project Issue is
more appropriate for the LibreOffice needs. There is a table that compares
the ticketing system available for Drupal as native modules:
http://groups.drupal.org/node/17948
Kind regards
--
http://www.cjenkins.net/
http://csl-tec.softwarelibrecr.org/
--
E-mail to website+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.