Project

Profile

Help

Task #90 ยป Task #115 - 2015-01-06T15_18_16Z.eml

rbarlow, 01/06/2015 04:18 PM

 
Return-Path: <rbarlow@redhat.com>
Received: from mi014.mc1.hosteurope.de ([80.237.138.241]) by wp245.webpack.hosteurope.de running ExIM with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1Y8VtP-0004Ps-Ci; Tue, 06 Jan 2015 16:17:59 +0100
Received: from mx1.redhat.com ([209.132.183.28]) by mx0.webpack.hosteurope.de (mi014.mc1.hosteurope.de) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1Y8VtO-0008UC-Bp for dropbox+pulp+c71e@plan.io; Tue, 06 Jan 2015 16:17:59 +0100
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t06FHsrS022557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <dropbox+pulp+c71e@plan.io>; Tue, 06 Jan 2015 10:17:54 -0500
Received: from where.usersys.redhat.com (dhcp129-96.rdu.redhat.com [10.13.129.96]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t06FHrxw009287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <dropbox+pulp+c71e@plan.io>; Tue, 06 Jan 2015 10:17:54 -0500
Date: Tue, 06 Jan 2015 10:17:53 -0500
From: Randy Barlow <rbarlow@redhat.com>
To: Pulp <dropbox+pulp+c71e@plan.io>
Message-ID: <54ABFCA1.6070807@redhat.com>
In-Reply-To: <redmine.issue-90.20150106144605@plan.io>
References: <redmine.issue-90.20150106144605@plan.io>
Subject: Re: [Pulp - Task #90] (NEW) Move RFEs from Bugzilla to Redmine
Mime-Version: 1.0
Content-Type: multipart/signed;
boundary=juEk6mghddgTboc2g4jIaFDITF7Uiw01P;
charset=UTF-8;
micalg=pgp-sha1;
protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Delivery-date: Tue, 06 Jan 2015 16:17:59 +0100
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
Thunderbird/31.3.0
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-HE-Spam-Level: -------
X-HE-Spam-Score: -7.0
X-HE-Spam-Report: Content analysis details: (-7.0 points) pts rule name
description ---- ----------------------
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
Sender listed at http://www.dnswl.org/, high trust [209.132.183.28 listed in
list.dnswl.org] -2.0 MULTIPART_SIGNED Contains a signed message (signature
attached)
X-HE-SPF: PASSED
Envelope-to: dropbox+pulp+c71e@plan.io

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--juEk6mghddgTboc2g4jIaFDITF7Uiw01P
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 01/06/2015 09:46 AM, Brian Bouterse wrote:
> Once a RFE is copied into Redmine, the bugzilla RFE should be CLOSED
> with a yet-to-be-created-in-bugzilla status of 'MOVED_TO_REDMINE'.
> Ideally, a custom field would be added to the Pulp Bugzilla that would
> allow the redmine issue to be tracked when the bugzilla RFE is closed.
> If that is not possible, then a comment can be added with the URL to th=
e
> new location in Redmine.

The rest of this all sounds fine, but I doubt we will be able to get
special closed statuses or special fields in BZ. I think closing it with
a final comment of "moved to <link>, please follow the issue there" or
something will suffice.

I also think it would be good to think about if we can include the CC
list, if possible. That may be tricky though, as it will probably
require adding users to our Redmine instance, and perhaps we don't want
to do that.

On 01/06/2015 09:46 AM, Pulp wrote:
> --- Please write your response above this line ---
> =

> Issue #90 has been reported by Brian Bouterse.
> -----------------------------------------------------------------------=
-
> =

> =

> Task #90: Move RFEs from Bugzilla to Redmine
> <https://pulp.plan.io/issues/90>
> =

> * Author: Brian Bouterse
> * Status: NEW
> * Priority: Normal
> * Assignee:
> * Category:
> * Sprint/Milestone: =

> =

> Currently bugzilla.redhat.com has many feature requests in it. These
> feature requests (RFEs) need to be copied from Bugzilla and into Redmin=
e.
> =

> This task involves migrating data between the systems using the Bugzill=
a
> and Redmine APIs in an automated way.
> =

> When moving a RFE, you'll have to do the following:
> 1) Move the following fields: description, priority, severity, status,
> reporter, assignee, QA-contact, version, and target release.
> 2) It would be good if the entire history of the bug/RFE were added int=
o
> the notes or appended to the description in redmine.
> 3) Component is also good to be preserved, but you'll have to find
> equivalent ones in Redmine.
> 4) Move any attachments also
> 5) Add a link on the redmine issue that links back to the original
> bugzilla location
> 6) Mark the redmine issue as a 'Story'
> =

> Note: you do NOT need to worry about 'blocks' or 'depends' relationship=
s
> yet, those will be handled in a separate story.
> =

> Once a RFE is copied into Redmine, the bugzilla RFE should be CLOSED
> with a yet-to-be-created-in-bugzilla status of 'MOVED_TO_REDMINE'.
> Ideally, a custom field would be added to the Pulp Bugzilla that would
> allow the redmine issue to be tracked when the bugzilla RFE is closed.
> If that is not possible, then a comment can be added with the URL to th=
e
> new location in Redmine.
> =

> Bugzilla RFEs contain the string 'rfe' in them or the keyword
> 'FutureFeature'. I have created a bugzilla search^0 <#fn0> which should=

> bugs which match either of these. There are ~125 bugs listed.
> =

> [0]: http://tinyurl.com/k2jfnwn
> =

> -----------------------------------------------------------------------=
-
> =

> You have received this notification because you have either subscribed
> to or are involved in a project on pulp Planio.
> To change your notification preferences, please click here:
> https://pulp.plan.io/my/account
> =

> =

> =

> This notification was cheerfully delivered by <https://plan.io/>
> =

> Planio <https://plan.io/>
> =




--juEk6mghddgTboc2g4jIaFDITF7Uiw01P
Content-Type: application/pgp-signature;
charset=UTF-8;
name=signature.asc
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUq/yhAAoJEIyFaKUJtmpil8sP+gJQZV2M7cEAIiowKJyUIRfs
nm/6qpuugVrEBtiCsf7dAdqdkfwthy+xMbFFw1vVegoJpgzQKZXLkhvQ4l6rXRD2
rC1OTthJ+NDfy791WebQcfmg8xPkjr7RseGVtmuyfBMX2yn+8u6lw+mCn1XMz+N0
QXfUaeDJZMVlDbXSlSdn5SjUg2fv1fevuOAq1RzYp2dZtd87kjEu0C4CS383qCR0
ThlzAClqHsI4qATH55cHiEKlRhHnuXxinTuwSCrnq+HVyUKkadU9uoCdzcpUJ/f1
sjwZUViwNXerpssSyk5g2JF9oitxi7SKlo9ZbRPLGH329b1RuGcf9ypre8jGL1O0
aOj4gFcnkNBwz/Ip7GojX3lGhsUx6SzWMA4zmMUl3NnKdvh5Am7Uf5bDtqRdohvi
Vz70fzfFXoqkKEu/aBM7/4xNaS0EOJg2esTnSjgkrlnwt7g4iTlcXukP916v+po+
ch7IU1mTpCSvf05bTqkxMpfzSnKpUqMRG5DNpKCDM+Nqtil0zRpyaV1rjTlQbePx
zx3L7efqjR5qVdLCIkh1wYciMeU0P0aax+xy12ZGFlRtkZnW+MDbac0oS6V5fUB4
ANmzCkiCp/0yquGCV569F6zmBJGYYxpRsbm125j6+ZD5hVvgUPlE2I15ICkBK40D
4aupJpS8iSOGIxMVHu6c
=Zuc8
-----END PGP SIGNATURE-----

--juEk6mghddgTboc2g4jIaFDITF7Uiw01P--
    (1-1/1)