lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uwe Schindler <>
Subject RE: jira tracking of issues fixed in 4.0-ALPHA
Date Mon, 02 Jul 2012 20:17:54 GMT
I think for this case, the much easier fix would be to rename the 4.0 version to 4.0-alpha
and create a new 4.0 one. All not yet fixed would get this new version as fix version.
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen

Uwe Schindler <> schrieb:

On my own JIRA server I have a groovy scripting plugin installed
( This
one can do this very simple and sophisticated. I did it several times on But of course at Apache this is harder. You also
need to know lots of API internals, because you are scripting the internal
JIRA API. But you can apply all "fixes" on a bunch of issues, preselected by
a filter like yours.

Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen

> -----Original Message-----
> From: Chris Hostetter []
> Sent: Monday, July 02, 2012 7:56 PM
> To: Lucene Dev
> Subject: jira tracking of issues fixed in 4.0-ALPHA
> Now that we have a 4.0-ALPHA version listed in Jira, it will be easy in
the future
> to record if a bug affected 4.0-ALPHA but was fixed in 4.0 (final).
> For all of the existing issues however ... things are complicated.
> I was hoping to do a Bulk edit of all issues matching this query...
> 	status = Resolved and
> 	resolutiondate < '2012-06-25 18:59' and
> 	fixVersion = '4.0'
> ...and add "fixVersion=4.0-ALPHA" to those issues (that date corrisponds
to the
> svn r# rmuir used for the alpha). The problem with this is that it will
> the entire fixVersion field -- so if an issue currently says
"fixVersion=3.6, 4.0"
> we will lose the information that it was fixed in 3.6.
> that seems worse then just leaving things alone.
> I considered briefly that we could add a "label" to all of the issues, but
> editing labels has the same behavior -- all existing labels are deleted,
and it
> looks like we have about 60 resolved 4.0 issues that actaully have labels
> them (how important those are i don't know)
> So I'm not sure that there is anything we can really do here.
> Anyone have any suggestions for ways we can *add* 4.0-ALPHA to the
> fixVersion for the 1000+ jira issues where it's appropriate?
> (feel free to SOLR-3590 as a test issue for bulk updates, that's why i
created it)
> -Hoss

> To unsubscribe, e-mail:
> For additional commands, e-mail:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message