We have been using JTrac in our organization for over six
months now with
encouraging results. I badly needed some of the new features
introduced in
2.1. Unfortunately we could not migrate to 2.1 Beta due to
bugs with the
related item functionality!
With the limited set of developers actively working on
JTrac, we should
concentrate on core features/bugs fixes rather than trying
to build add-on
features like a Wiki engine. WiKi is not an essential
component of issue
tracking. My personal opinion is that we should be able to
figure out ways
to integrate best of breed open source WiKis with JTrac
rather than spending
time trying to embed a WiKi within JTrac.
I think interfacing with third party products (LDAP support,
Subversion
integration, etc.) will add more value that trying to embed
them within
JTrac.
We also migrated to Subversion (from VSS) recently. Here is
how Jtrac can
integrate with Subversion:
1. TortoiseSVN client can be easily configured to prompt for
a JTrac ID when
checking in changes to the Subversion repository. With
friendly URLs in
JTrac 2.1, we can easily configure Tortoise to create a
hyperlink to the
JTrac item ID from the Subversion commit log.
2. Programmatically add a history record in Jtrac from a
Subversion post
commit trigger with the list of files that were checked in
for a particular
jTrac task. We use https to access Subversion. So we can
easily link to a
file in Subversion with a URL in Jtrac comment text. We will
need JTrac to
support HTML tags for this.
Thanks,
Saurabh
-----Original Message-----
From: j-trac-users-bounces lists.sourceforge.net
[mailto:j-trac-users-bounceslists.sourceforge.net] On
Behalf Of
thebugslayer
Sent: Saturday, October 20, 2007 7:21 AM
To: JTrac users mailing-list
Subject: Re: [jtrac-users] future roadmap
Peter,
I have used VQWiki and XWiki (just as end user though) and
they both
are ready to use out of the box. VQWiki is simpler and
lighter, while
XWiki seems to be bigger but with larger user community with
richer
feature set.
I have not dealt with Radeox.
In regardless, I think one of the main attraction and good
feature of
any wiki should provide is API set to easily add different
set of
syntax parser. As we already know almost every engine out
there has
it's own syntax rules. Been able to a most popular rule like
in
Confluence etc, will allow user to migrate easily.
-Zemian
On 10/19/07, Peter Thomas <ptrthomasgmail.com> wrote:
> Hi,
>
> Appreciate your interest and I completely agree that
Wiki + Subversion is
a
> must.
>
> JTrac development has admittedly slowed down over the
last 2-3 months.
Some
> patches have started to come in though and we hope to
have development in
> full-swing very soon. (Day-job kinda getting in the
way). Honestly never
> expected that something that sounds as simple as an
issue-tracker would
have
> so many layers to it 
>
> Any ideas on the wiki-engine to embed would be welcome.
I was thinking of
> Radeox, bit about it here:
>
>
http://stephan.reposita.org/archives
/2007/08/20/forking-radeox-a-new-wiki-re
nder-engine/
>
> Thanks,
>
> Peter.
>
>
> On 10/19/07, thebugslayer <thebugslayergmail.com> wrote:
> >
> > Hi Peter,
> >
> > I really like to see jTrac providing similar
features that
> > Trac(python) provides. Wiki+Issues+Subversion are
just a must have,
> > attractive combo for any project management. I
would trade war
> > deployment vs TracInstall anytime.
> >
> > Any news as to jTrac's future roadmap and
release?
> >
> > --
> > theBUGslayer
> >
> >
>
------------------------------------------------------------
-------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?
Stop.
> > Now Search log events and configuration files
using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > j-trac-users mailing list
> > j-trac-userslists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/j-trac-use
rs
> >
>
>
>
------------------------------------------------------------
-------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?
Stop.
> Now Search log events and configuration files using
AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> j-trac-users mailing list
> j-trac-userslists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/j-trac-use
rs
>
>
--
theBUGslayer
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
j-trac-users mailing list
j-trac-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/j-trac-use
rs
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
j-trac-users mailing list
j-trac-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/j-trac-use
rs
|