Mailing-List: contact allura-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of object.rexx@gmail.com
 designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <EE2C0F491A8A41D6971B61E6DB4A27E1@geek.net>
References: 
 <CAPJz3GtYg8VZk04YHc7-6TFY0i+KBNxdzD+Y7gAoHT-K0rgYJg@mail.gmail.com>
	<EE2C0F491A8A41D6971B61E6DB4A27E1@geek.net>
Date: Tue, 21 Aug 2012 09:32:37 -0400
Message-ID: 
 <CAPJz3Gs3DpK4mX+5ouVENaP0A8xDsJ78aAd+EoazYDqFOc4-KQ@mail.gmail.com>
Subject: Re: Linking commits and tickets
From: Rick McGuire <object.rexx@gmail.com>
To: allura-users@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec55553f2ddc6b504c7c6a859

--bcaec55553f2ddc6b504c7c6a859
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Aug 21, 2012 at 9:22 AM, Tim Van Steenburgh <tvansteenburgh@geek.net
> wrote:

>  Hi Rick,
>
> You can link to a ticket from a commit message (or any markdown-parsed
> text) with a link like: [#1234] (where 1234 is the ticket number).
>

How does this work when the project has multiple trackers set up?  For
example, we have one tracker system for Bugs and a separate one for Feature
Requests (this is a migrated sourceforge project).  Using, for example,
[#1] is ambiguous, since there are #1 tickets in two different trackers.

Rick


>
> Most artifacts, if linked to, will automatically link back to the
> referrer. Commit messages are an exception (at the moment - this will be
> fixed eventually). So, when you link to something (a ticket, for example)
> from a commit message, that ticket will not automatically link back to the
> commit. But, you can link to the commit manually with:
>
> [b58f38] (first 6 chars of git or hg commit hash), or
> [r32] (svn revision number)
>
> HTH,
>
> --
> Tim Van Steenburgh
>
> On Tuesday, August 21, 2012 at 8:43 AM, Rick McGuire wrote:
>
> The Wiki lists being able to link commits and tickets together, but I've
> not found anything that describes how to enable/use this feature.  Is this
> something that happens automatically, or do you just use markdown to
> include links to the ticket item in the commit comments?
>
> Rick
>
>
>
> ====
> This e- mail message is intended only for the named recipient(s) above. It
> may contain confidential and privileged information. If you are not the
> intended recipient you are hereby notified that any dissemination,
> distribution or copying of this e-mail and any attachment(s) is strictly
> prohibited. If you have received this e-mail in error, please immediately
> notify the sender by replying to this e-mail and delete the message and any
> attachment(s) from your system. Thank you.
>
>

--bcaec55553f2ddc6b504c7c6a859
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Aug 21, 2012 at 9:22 AM, Tim Van=
 Steenburgh <span dir=3D"ltr">&lt;<a href=3D"mailto:tvansteenburgh@geek.net=
" target=3D"_blank">tvansteenburgh@geek.net</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">

                <div>
                    Hi Rick,
                </div><div><br></div><div>You can link to a ticket from a c=
ommit message (or any markdown-parsed text) with a link like: [#1234] (wher=
e 1234 is the ticket number).</div></blockquote><div><br></div><div>How doe=
s this work when the project has multiple trackers set up? =A0For example, =
we have one tracker system for Bugs and a separate one for Feature Requests=
 (this is a migrated sourceforge project). =A0Using, for example, [#1] is a=
mbiguous, since there are #1 tickets in two different trackers.=A0</div>
<div><br></div><div>Rick</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div><br></div><div>Most artifacts, if linked to, will automatically link b=
ack to the referrer. Commit messages are an exception (at the moment - this=
 will be fixed eventually). So, when you link to something (a ticket, for e=
xample) from a commit message, that ticket will not automatically link back=
 to the commit. But, you can link to the commit manually with:</div>
<div><br></div><div>[b58f38] (first 6 chars of git or hg commit hash), or</=
div><div>[r32] (svn revision number)</div>
                <div><div><br></div><div>HTH,</div><div><br></div><div>--=
=A0</div><div>Tim Van Steenburgh</div><div><br></div></div><div class=3D"im=
">
                =20
                <p style=3D"color:#a0a0a8">On Tuesday, August 21, 2012 at 8=
:43 AM, Rick McGuire wrote:</p>
                <blockquote type=3D"cite" style=3D"border-left-style:solid;=
border-width:1px;margin-left:0px;padding-left:10px">
                    <span><div><div>The Wiki lists being able to link commi=
ts and tickets together, but I&#39;ve not found anything that describes how=
 to enable/use this feature. =A0Is this something that happens automaticall=
y, or do you just use markdown to include links to the ticket item in the c=
ommit comments?<div>

<br></div><div>Rick</div>
</div></div></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
           =20
<br></div>
=3D=3D=3D=3D<br>This e- mail message is intended only for the named recipie=
nt(s) above. It may contain confidential and privileged information. If you=
 are not the intended recipient you are hereby notified that any disseminat=
ion, distribution or copying of this e-mail and any attachment(s) is strict=
ly prohibited. If you have received this e-mail in error, please immediatel=
y notify the sender by replying to this e-mail and delete the message and a=
ny attachment(s) from your system. Thank you.<br>
<br></blockquote></div><br>

--bcaec55553f2ddc6b504c7c6a859--