Re: [sipcore] Tracker Etiquette

"Worley, Dale R (Dale)" <dworley@avaya.com> Wed, 01 September 2010 02:21 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D31BF3A6A1A for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 19:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level:
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLLfwVMtQVPH for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 19:21:20 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id ABE543A6859 for <sipcore@ietf.org>; Tue, 31 Aug 2010 19:21:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,301,1280721600"; d="scan'208";a="205412315"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 31 Aug 2010 22:21:43 -0400
X-IronPort-AV: E=Sophos;i="4.56,301,1280721600"; d="scan'208";a="510698961"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 Aug 2010 22:21:42 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 31 Aug 2010 22:21:42 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Adam Roach <adam@nostrum.com>, SIPCORE <sipcore@ietf.org>
Date: Tue, 31 Aug 2010 22:21:41 -0400
Thread-Topic: [sipcore] Tracker Etiquette
Thread-Index: ActJRrqW58iUkq/gSh6KJTzu5F5VjQANKOqt
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C04@DC-US1MBEX4.global.avaya.com>
References: <4C7D5E9C.9090908@nostrum.com>
In-Reply-To: <4C7D5E9C.9090908@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] Tracker Etiquette
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 02:21:26 -0000

I've been assuming that the tracker is to be used much like a technical support tracker -- it's assumed that duplicate and mistaken tickets will be entered, and often variants of existing tickets, and that there are facilities for easily closing tickets that prove to be useless, and for consolidating tickets that are partially or completely duplicates.  Maybe I'm mistaken; I'm assuming that closing a ticket is not difficult.

In regard to putting something in the "ticket name" to indicate the document in question:  I see a data field "Component" for which one can select the value "4244bis".  I've been assuming that is how one identifies the tickets that are relevant to 4244bis.  Is this not the correct thing to do?  I do not see a data field named "ticket name".

Dale