Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57FDAD4D6 for ; Wed, 12 Dec 2012 07:49:38 +0000 (UTC) Received: (qmail 16874 invoked by uid 500); 12 Dec 2012 07:49:37 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 16840 invoked by uid 500); 12 Dec 2012 07:49:37 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 16815 invoked by uid 99); 12 Dec 2012 07:49:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2012 07:49:36 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.67.31.101] (HELO smtprelay06.ispgateway.de) (80.67.31.101) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2012 07:49:29 +0000 Received: from [10.128.0.3] (helo=exchange.df.eu) by smtprelay06.ispgateway.de with esmtps (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1Tih41-0007JO-7U for flex-dev@incubator.apache.org; Wed, 12 Dec 2012 08:49:09 +0100 Received: from ECCR06PUBLIC.exchange.local ([10.128.2.55]) by efe03.exchange.local ([10.128.0.3]) with mapi; Wed, 12 Dec 2012 08:49:09 +0100 From: "christofer.dutz@c-ware.de" To: "flex-dev@incubator.apache.org" Date: Wed, 12 Dec 2012 08:49:07 +0100 Subject: AW: Suggestion to commits and Jira Thread-Topic: Suggestion to commits and Jira Thread-Index: Ac3YPLEBU3u5d411Q1SsNT5Y0i+HnwAABNIQ Message-ID: <66E38C42347D6446BF7FCB22C3D3878072E2946220@ECCR06PUBLIC.exchange.local> References: <66E38C42347D6446BF7FCB22C3D3878072E2946217@ECCR06PUBLIC.exchange.local> In-Reply-To: Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Well it would be nice to be able to click on an issue and see what was done= to resolve it. Otherwise you would have to register for the commit list an= d keep everything in order to do searches there, which I think is relativel= y undesirable considering the current size of my pst-file. It's a feature t= hat comes almost for free and I think the benefits outweigh the cost by far= . But that's just my personal opinion ;-) -----Urspr=FCngliche Nachricht----- Von: Fr=E9d=E9ric THOMAS [mailto:webdoublefx@hotmail.com]=20 Gesendet: Mittwoch, 12. Dezember 2012 08:45 An: flex-dev@incubator.apache.org Betreff: Re: Suggestion to commits and Jira Hi Chris, I don't know for that, I used to work the same but here, in the commit mail= ling list, for each commit, you can see a link to viewvc with the diff for = each commit but sure, it would be nice to have the same in JIRA. - Fred -----Message d'origine----- From: christofer.dutz@c-ware.de Sent: Wednesday, December 12, 2012 8:38 AM To: flex-dev@incubator.apache.org Subject: Suggestion to commits and Jira Hi, I just wanted to have a look at what Jose did to fix a bug in the Mavenizer= .=20 My usual workflow for this is to go to the Jira Issue and select the "Sourc= e" tab. In all of the Jira+SVN/GIT combinations I have seen Jira displays t= he commits related to that particular issue. I couldn't find a single issue= in which Jira found anything. Is this feature not turned on or did simply no one check in any code with a= comment containing the Jira issue id of the related issue? I would strongly suggest to link the code repo and Jira and to prefix commi= t-comments with Jira issue Id of the issue the checkin relates to (Ideally = with the title of the Issue) in order to get this cool bonus functionality.= If one commit addresses a bunch of issues simply mentioning them all in th= e commit statement, would also make that particular cheking appear on all o= f these issues detail-pages. Just a suggestion :) Chris