Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 66.249.82.231 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Thkm+bJfni1Lm2gfRoD7ZRrEtGHi0vc1bIuURXnXfqh6ROL1H2nKGhieMyZj48GVoBPDnYfeo3qEkNsrQN5/wEwPmGfIwdehBE/wC+cvWuITbxt7/izID9GRj0NcN8zHpca4MSgnRdSSeM7s8oyTpQ4qJHqKsNK0aW+4s3qnP1o=
Message-ID: <d45b08f00709260153k13d1228en4a67e9b595698ee1@mail.gmail.com>
Date: Wed, 26 Sep 2007 10:53:46 +0200
From: "Emmanuel Lecharny" <elecharny@gmail.com>
Reply-To: elecharny@iktek.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [research] Connection between SVN mailing list and JIRA.
In-Reply-To: <3737e9020709252246p61ee4f44tf2d997fd42b0458@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <3737e9020709252042m5bb1d1akb5ce8e20a2f5d15d@mail.gmail.com>
	 <43b026c70709252201j3c6aab93k1300b928b041b679@mail.gmail.com>
	 <3737e9020709252246p61ee4f44tf2d997fd42b0458@mail.gmail.com>

Hi Yeliz,

when we fix a JIRA, and if there are not too many commits associated,
we generally copy/past the commits into the JIRA :

https://issues.apache.org/jira/browse/DIRSERVER-1029
https://issues.apache.org/jira/browse/DIRSERVER-1027
...

It's something we try to do as much as possible.

On 9/26/07, Yeliz Eseryel <yeliz2002@alum.syracuse.edu> wrote:
> Hi Chris,
> Ah yes, I am aware of this one. Yeah, it's a bit other way around.
> What I couldn't figure out was how to embed the related SVN commit
> comment into a report that shows all issues (for example take the
> report for "all" under the preset filters)
> Is there a way for that?
> Yeliz.
>
> On 9/26/07, Chris Custine <ccustine@apache.org> wrote:
> > Hi Yeliz!
> > There is actually a plugin in Jira that scans SVN commit comments for v=
alid
> > JIRA issues and then puts a nice link in the issue if there are any.  T=
his
> > is backwards from what you are asking, but its close.  You can see all
> > recent Subversion commits for the entire Apache Directory project here.=
  Of
> > course this is dependent on putting a valid Jira issue in the SVN commi=
t
> > message, so it is hard to enforce the practice.  Personally, I am a hab=
itual
> > commit commenter, so I have a personal edict of never commiting without=
 a
> > valid JIRA issue to reference in the comment.
> >
> > Hope this helps,
> > Chris
> >
> >
> > On 9/25/07, Yeliz Eseryel <yeliz2002@alum.syracuse.edu> wrote:
> > > Hi guys,
> > > I am trying to link the changes that are made in SVN, that are
> > > reported through SVN mailing list and the issues that are opened and
> > > closed in JIRA. I couldn't see an ID or anything that seems to be
> > > common among the two. Do you have any ideas how I can link the two
> > > logically?
> > >
> > > Also generally, do the people who commit changes to SVN go ahead and
> > > update JIRA? or is it typically someone else who does the updating (I
> > > am not asking about the ideal case of what should happen. I am asking
> > > about what is typically happening today.)
> > >
> > > Thanks.
> > > Yeliz.
> > >
> > > --
> > > Yeliz Eseryel
> > > Ph.D Student in Information Science & Technology
> > > Syracuse University School of Information Studies
> > > http://enterprisesystems.blogspot.com
> > >
> > >
> > -----------------------------------------------------------------------
> > >
> >
> >
>
>
> --
> Yeliz Eseryel
> Ph.D Student in Information Science & Technology
> Syracuse University School of Information Studies
> http://enterprisesystems.blogspot.com
>
> -----------------------------------------------------------------------
>


--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com