> -----Original Message-----
> From: David Weintraub [mailto:qazwart_at_gmail.com]
> Sent: Thursday, June 19, 2008 3:17 PM
> To: users_at_subversion.tigris.org
> Subject: Re: Tickets
>
>
> You could do something similar with Subversion's revision properties,
> but there are several limits that must be overcome:
>
> * Revision properties only have a single value. For example, you could
> have a revision property of "jira:ticket" which could contain the Jira
> ticket that was involved with that revision, but you can't say what
> the status of that ticket is, who fixed it, its description, etc.
I disagree. If I wanted to manage ticket status, I would use
the ticket app which has an interface specifically designed to handle
and manage up-to-date ticket information. If anything, I would want to
be able to checkout from the ticket system, in order to automatically
apply ticket number(s) to the subversion workspace and to automatically
update the ticket status to "Bob is now working on Tickets 1, 2 and 3 on
branch X."
Subversion is a database for use by DBAs (aka coders.) Ticket
management needs a separate, dedicated, pretty interface that
non-DBAs/coders (aka managers, testers, report-o-philes) can also use.
> * You can't query on revision properties: For example, I can't say
> "Show me all revisions that have a property of "jira:ticket" which has
> a value of "BUG-1323".
You can query on revision properties, it's just not efficient.
You would need to dump all the revision properties for all revisions and
then filter them.
Or you cache the information in the ticket system's database via
hooks.
> * Revisions can only have a single instance of a particular revision
> property. You can't have a revision with two instances of
> "jira:ticket" to show that this revision fixed both BUG-1234 and
> BUG-1384.
Not true. You can assign multiple values to a single property
by making the value comma separated:
jira:ticket = 1234,2345,4578
But obviously, lookups are inefficient.
You can also have the property be the value, in order to support
multiple values:
jira:ticket_1234 = ''
jira:ticket_2345 = ''
jira:ticket_4578 = ''
> Of course, the answer whether Subversion has a ticketing system is
> still "no", but it might be something interesting to consider in
> future revisions of Subversion.
It would be peachy keen if svn had indexed/queryable revision
properties. You can already integrate other ticket systems by assigning
a ticket # to a revision via a property or in the commit comment.
However, doing lookups is a tad slow due to having to 'svn log' or 'svn
proplist' the entire branch before filtering the data.
*****
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA625
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-20 15:56:02 CEST