You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Brian Cho <ch...@gmail.com> on 2015/08/06 11:38:00 UTC
Apology for the spam, don’t close issues, and JIRA bulk edit
Hi,
As part of the job of Release Manager, I went through JIRA and changed all
“Fix Version/s” to 0.12. This lets us generate the release notes [1].
However, this didn’t go as cleanly as I wished. Some observations:
1. I’m sorry about the amount spam generated. Not only is it annoying, but
it buries real work :(
2. We should make a policy of not closing issues before a release. In state
“closed” the fix version can’t be changed. The issues have to be re-opened
to do that. It’s annoying and it also ends up changing the resolution date.
So we now have a bunch of issues that were resolved a few minutes ago :(
3. JIRA *does* have bulk edit under “Tools”. It’s not all that intuitive
though. If any one of the selected edits doesn’t apply, it gives an error
[2]. This caught me because I didn’t know about 2 yet, so I assumed we just
couldn’t bulk edit. I did a lot of manual clicking before I figured out
that it does indeed work.
Again, I apologize for the spam interrupting everyone’s workflow!
Thanks,
Brian
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12332143
[2] "NOTE: You do not have permission to edit the selected 1 issues or at
least one issue has a status that forbids editing."
Re: Apology for the spam, don’t close issues, and JIRA bulk edit
Posted by Byung-Gon Chun <bg...@gmail.com>.
Thanks, Brian.
Can we use "Resolved" all the time?
Is there any incentive to use "Closed"?
On Fri, Aug 7, 2015 at 10:10 AM, Brian Cho <ch...@gmail.com> wrote:
> Markus, Julia:
>
> You’re right. A policy to make sure the Fix version number is set _on
> resolution_ will work. +1 on that.
>
> What I was trying to say is that “Closed” and “Resolved” are not the same
> thing. With “Resolved”, the Fix version for the issue can still be edited.
> With “Closed” the issue has to be re-opened to do that. But this won’t
> matter if we always set the Fix version when the resolution is done.
>
> On a related note, we shouldn’t set the fix version for issues that are
> still open. In that case, the issues show up in the release notes page [1]
> even though they haven’t been resolved. I’ll have to go through those in a
> couple hours.
>
> [1]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12332143
>
> Thanks,
> Brian
>
> On Fri, Aug 7, 2015 at 1:58 AM, Julia Wang (QIUHE) <
> Qiuhe.Wang@microsoft.com
> > wrote:
>
> > I was facing the same issue in last release. We should make sure to set
> > the version number when resolving it, instead of changing it one by one
> by
> > release manager.
> >
> > -----Original Message-----
> > From: Markus Weimer [mailto:markus@weimo.de]
> > Sent: Thursday, August 6, 2015 8:46 AM
> > To: dev@reef.incubator.apache.org
> > Subject: Re: Apology for the spam, don’t close issues, and JIRA bulk edit
> >
> > Hi,
> >
> > no worries, Brian. On the downside, you will never be able to send me
> > email again, as my Spam filter is on to you :-)
> >
> >
> > On 2015-08-06 02:38, Brian Cho wrote:
> > > 2. We should make a policy of not closing issues before a release. In
> > > state “closed” the fix version can’t be changed. The issues have to be
> > > re-opened to do that. It’s annoying and it also ends up changing the
> > resolution date.
> > > So we now have a bunch of issues that were resolved a few minutes ago
> > > :(
> >
> > I don't follow. You are suggesting to never close issues? I thought we'd
> > be fine if we make sure to always record the correct fix issue while
> > closing.
> >
> > Markus
> >
>
--
Byung-Gon Chun
Re: Apology for the spam, don’t close issues, and JIRA bulk edit
Posted by Brian Cho <ch...@gmail.com>.
Markus, Julia:
You’re right. A policy to make sure the Fix version number is set _on
resolution_ will work. +1 on that.
What I was trying to say is that “Closed” and “Resolved” are not the same
thing. With “Resolved”, the Fix version for the issue can still be edited.
With “Closed” the issue has to be re-opened to do that. But this won’t
matter if we always set the Fix version when the resolution is done.
On a related note, we shouldn’t set the fix version for issues that are
still open. In that case, the issues show up in the release notes page [1]
even though they haven’t been resolved. I’ll have to go through those in a
couple hours.
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315820&version=12332143
Thanks,
Brian
On Fri, Aug 7, 2015 at 1:58 AM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
> wrote:
> I was facing the same issue in last release. We should make sure to set
> the version number when resolving it, instead of changing it one by one by
> release manager.
>
> -----Original Message-----
> From: Markus Weimer [mailto:markus@weimo.de]
> Sent: Thursday, August 6, 2015 8:46 AM
> To: dev@reef.incubator.apache.org
> Subject: Re: Apology for the spam, don’t close issues, and JIRA bulk edit
>
> Hi,
>
> no worries, Brian. On the downside, you will never be able to send me
> email again, as my Spam filter is on to you :-)
>
>
> On 2015-08-06 02:38, Brian Cho wrote:
> > 2. We should make a policy of not closing issues before a release. In
> > state “closed” the fix version can’t be changed. The issues have to be
> > re-opened to do that. It’s annoying and it also ends up changing the
> resolution date.
> > So we now have a bunch of issues that were resolved a few minutes ago
> > :(
>
> I don't follow. You are suggesting to never close issues? I thought we'd
> be fine if we make sure to always record the correct fix issue while
> closing.
>
> Markus
>
RE: Apology for the spam, don’t close issues, and JIRA bulk edit
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
I was facing the same issue in last release. We should make sure to set the version number when resolving it, instead of changing it one by one by release manager.
-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de]
Sent: Thursday, August 6, 2015 8:46 AM
To: dev@reef.incubator.apache.org
Subject: Re: Apology for the spam, don’t close issues, and JIRA bulk edit
Hi,
no worries, Brian. On the downside, you will never be able to send me email again, as my Spam filter is on to you :-)
On 2015-08-06 02:38, Brian Cho wrote:
> 2. We should make a policy of not closing issues before a release. In
> state “closed” the fix version can’t be changed. The issues have to be
> re-opened to do that. It’s annoying and it also ends up changing the resolution date.
> So we now have a bunch of issues that were resolved a few minutes ago
> :(
I don't follow. You are suggesting to never close issues? I thought we'd be fine if we make sure to always record the correct fix issue while closing.
Markus
Re: Apology for the spam, don’t close issues, and JIRA bulk edit
Posted by Markus Weimer <ma...@weimo.de>.
Hi,
no worries, Brian. On the downside, you will never be able to send me
email again, as my Spam filter is on to you :-)
On 2015-08-06 02:38, Brian Cho wrote:
> 2. We should make a policy of not closing issues before a release. In state
> “closed” the fix version can’t be changed. The issues have to be re-opened
> to do that. It’s annoying and it also ends up changing the resolution date.
> So we now have a bunch of issues that were resolved a few minutes ago :(
I don't follow. You are suggesting to never close issues? I thought we'd
be fine if we make sure to always record the correct fix issue while
closing.
Markus