Mailing-List: contact dev-help@tiles.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tiles.apache.org
Received-SPF: pass (athena.apache.org: domain of gcatd-dev@m.gmane.org
 designates 80.91.229.12 as permitted sender)
To: dev@tiles.apache.org
connect(): No such file or directory
From: Mck <mick@semb.wever.org>
Subject: [OT] jira workflow   WAS: Commented: (TILES-506) Fix link to jira
 under "Project  Information --> Issue tracking"
Date: Tue, 04 May 2010 10:02:55 +0200
Lines: 46
Message-ID: <1272960159.15037.43.camel@localhost.localdomain>
References: <30330667.165141272045170121.JavaMail.jira@thor>
	 <1515259.61272729236161.JavaMail.jira@thor>
	 <1272803734.10088.61.camel@localhost.localdomain>
	 <y2kaae96ca1005020506ld99f86f5g85a8c896babe6d57@mail.gmail.com>
	 <1272827678.12298.14.camel@localhost.localdomain>
	 <s2yaae96ca1005030026gdab51e6ey400998537740cace@mail.gmail.com>
	 <1272914174.18975.8.camel@localhost.localdomain>
	 <n2jaae96ca1005031147oed5d92bek649a491e33390139@mail.gmail.com>
	 <1272954050.10890.23.camel@localhost.localdomain>
	 <x2maae96ca1005040035h4b44e0d4s1e419f5173a9bda@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1";
 protocol="application/pgp-signature"; boundary="=-BAIyk9g1UzL7DZbWGM29"
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: home.schibsted.no
In-Reply-To: <x2maae96ca1005040035h4b44e0d4s1e419f5173a9bda@mail.gmail.com>
X-Mailer: Evolution 2.28.3.1 

--=-BAIyk9g1UzL7DZbWGM29
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2010-05-04 at 09:35 +0200, Antonio Petrelli wrote:
> Not the issue, the version in the "Fix for" field of Jira issues. The
> issues should be moved to a higher version.

Couldn't this just be done in the same bulk step as when you change all
the issues to closed?
That is all those resolved issues remain resolved until one of the "test
builds" is successfully made into a release X.Y.Z. At that point then
all those resolved issues are bulk changed to "closed" and "Fix for
X.Y.X".

It's not so important, as i've marked the subject OT, but i'm presuming
that apache doesn't give anyone here the rights to remove the "resolved"
state from the TILES jira project, and so am wondering if there's a way
to better use it. Nobody likes dead wood!

> Anyway, your questions are always welcome!=20

Thanks. There are many ways of organising an issue tracker so it's nice
to know how tiles does it, and to just learn another way.=20

~mck

--=20
"The rainbow would not be without first the rain." D Donche Jr=20
| http://semb.wever.org | http://sesat.no | http://finn.no |

--=-BAIyk9g1UzL7DZbWGM29
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEABECAAYFAkvf1J8ACgkQkdPrePiuutOL/ACfaNWrbSJDwfeTzlGCax0uxEIR
q0UAnjz3OTYTHehsmffNs8mXsz/wjsKp
=kvPm
-----END PGP SIGNATURE-----

--=-BAIyk9g1UzL7DZbWGM29--