You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Hongze Zhang <no...@126.com> on 2019/04/29 14:48:21 UTC
Clean up JIRA tickets
Hi all,
As I have suggested on a related thread[1] started by Stamatis, I am planning to close the JIRA tickets that are marked as status "RESOLVED" but bound with an earlier fix version. Say, if a ticket is marked "RESOLVED", and its fix version is provided but not one of our unreleased versions 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going to be closed.
Here is a link to the full list (currently 78 tickets in total):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
I'll close them by the ascending order of JIRA ID respectively. If you used to participate in the discussion of any issue on the list, and you think it is too early to close, please feel free to reopen and add some follow-up comments.
Thanks,
Hongze
[1] https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
Re: Clean up JIRA tickets
Posted by Hongze Zhang <no...@126.com>.
Thanks a lot for the tips, Kevin! This is indeed what I need. However I didn't notice the existing of the tool before. ;)
Hongze
> On Apr 30, 2019, at 00:11, Kevin Risden <co...@gmail.com> wrote:
>
> You can do this as a bulk transition to avoid emailing everyone of the
> change. If you select "Tools" -> "Bulk change".
>
> Kevin Risden
>
>
> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
>
>> Hi all,
>>
>> As I have suggested on a related thread[1] started by Stamatis, I am
>> planning to close the JIRA tickets that are marked as status "RESOLVED" but
>> bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
>> and its fix version is provided but not one of our unreleased versions
>> 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
>> to be closed.
>>
>> Here is a link to the full list (currently 78 tickets in total):
>>
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>>
>> I'll close them by the ascending order of JIRA ID respectively. If you
>> used to participate in the discussion of any issue on the list, and you
>> think it is too early to close, please feel free to reopen and add some
>> follow-up comments.
>>
>> Thanks,
>> Hongze
>>
>>
>> [1]
>> https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>>
>
Re: Clean up JIRA tickets
Posted by Hongze Zhang <no...@126.com>.
Thanks for the help and clarifying, Francis.
Hongze
------ Original Message ------
From: "Francis Chuang" <fr...@apache.org>
To: dev@calcite.apache.org
Sent: 2019/4/30 6:23:01
Subject: Re: Clean up JIRA tickets
>This is because the option is only available to people with the Administrator role. It seems counter-intuitive, but according to the JIRA documentation, you need to be an administrator to do this: https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html
>
>I've given you the administrator role on JIRA, so the option will be available when you want to make a bulk transition next time.
>
>Volodymyr and I also encountered this problem last year when we were release managers for the first time:
>- https://lists.apache.org/thread.html/21ba575b7adc5ac3e1520675136db501d0958641ce98f1d0a0d291c7@%3Cdev.calcite.apache.org%3E
>- https://lists.apache.org/thread.html/216c7fc441509f9da8c63937f30d5458a1222f475da89a4ec4417ece@%3Cdev.calcite.apache.org%3E
>
>Francis
>
>On 30/04/2019 3:58 am, Hongze Zhang wrote:
>>Thanks Josh, I noticed that the mails are sent, apologize to everyone being annoyed.
>>
>>Maybe I missed something but I re-checked the whole process of bulk operation and still didn't found such a button. Not sure if it is related to JIRA roles.
>>
>>Apologize again, please ignore these emails.
>>
>>Hongze
>>
>>
>>
>>>On Apr 30, 2019, at 01:21, Josh Elser <el...@apache.org> wrote:
>>>
>>>Yes, please check the "don't send emails" button in the future :)
>>>
>>>Thanks for cleaning them up, Hongze!
>>>
>>>On 4/29/19 12:11 PM, Kevin Risden wrote:
>>>>You can do this as a bulk transition to avoid emailing everyone of the
>>>>change. If you select "Tools" -> "Bulk change".
>>>>Kevin Risden
>>>>On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
>>>>>Hi all,
>>>>>
>>>>>As I have suggested on a related thread[1] started by Stamatis, I am
>>>>>planning to close the JIRA tickets that are marked as status "RESOLVED" but
>>>>>bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
>>>>>and its fix version is provided but not one of our unreleased versions
>>>>>1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
>>>>>to be closed.
>>>>>
>>>>>Here is a link to the full list (currently 78 tickets in total):
>>>>>
>>>>>
>>>>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>>>>>
>>>>>I'll close them by the ascending order of JIRA ID respectively. If you
>>>>>used to participate in the discussion of any issue on the list, and you
>>>>>think it is too early to close, please feel free to reopen and add some
>>>>>follow-up comments.
>>>>>
>>>>>Thanks,
>>>>>Hongze
>>>>>
>>>>>
>>>>>[1]
>>>>>https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>>>>>
>>
Re: Clean up JIRA tickets
Posted by Francis Chuang <fr...@apache.org>.
This is because the option is only available to people with the
Administrator role. It seems counter-intuitive, but according to the
JIRA documentation, you need to be an administrator to do this:
https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html
I've given you the administrator role on JIRA, so the option will be
available when you want to make a bulk transition next time.
Volodymyr and I also encountered this problem last year when we were
release managers for the first time:
-
https://lists.apache.org/thread.html/21ba575b7adc5ac3e1520675136db501d0958641ce98f1d0a0d291c7@%3Cdev.calcite.apache.org%3E
-
https://lists.apache.org/thread.html/216c7fc441509f9da8c63937f30d5458a1222f475da89a4ec4417ece@%3Cdev.calcite.apache.org%3E
Francis
On 30/04/2019 3:58 am, Hongze Zhang wrote:
> Thanks Josh, I noticed that the mails are sent, apologize to everyone being annoyed.
>
> Maybe I missed something but I re-checked the whole process of bulk operation and still didn't found such a button. Not sure if it is related to JIRA roles.
>
> Apologize again, please ignore these emails.
>
> Hongze
>
>
>
>> On Apr 30, 2019, at 01:21, Josh Elser <el...@apache.org> wrote:
>>
>> Yes, please check the "don't send emails" button in the future :)
>>
>> Thanks for cleaning them up, Hongze!
>>
>> On 4/29/19 12:11 PM, Kevin Risden wrote:
>>> You can do this as a bulk transition to avoid emailing everyone of the
>>> change. If you select "Tools" -> "Bulk change".
>>> Kevin Risden
>>> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
>>>> Hi all,
>>>>
>>>> As I have suggested on a related thread[1] started by Stamatis, I am
>>>> planning to close the JIRA tickets that are marked as status "RESOLVED" but
>>>> bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
>>>> and its fix version is provided but not one of our unreleased versions
>>>> 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
>>>> to be closed.
>>>>
>>>> Here is a link to the full list (currently 78 tickets in total):
>>>>
>>>>
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>>>>
>>>> I'll close them by the ascending order of JIRA ID respectively. If you
>>>> used to participate in the discussion of any issue on the list, and you
>>>> think it is too early to close, please feel free to reopen and add some
>>>> follow-up comments.
>>>>
>>>> Thanks,
>>>> Hongze
>>>>
>>>>
>>>> [1]
>>>> https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>>>>
>
Re: Clean up JIRA tickets
Posted by Hongze Zhang <no...@126.com>.
Thanks Josh, I noticed that the mails are sent, apologize to everyone being annoyed.
Maybe I missed something but I re-checked the whole process of bulk operation and still didn't found such a button. Not sure if it is related to JIRA roles.
Apologize again, please ignore these emails.
Hongze
> On Apr 30, 2019, at 01:21, Josh Elser <el...@apache.org> wrote:
>
> Yes, please check the "don't send emails" button in the future :)
>
> Thanks for cleaning them up, Hongze!
>
> On 4/29/19 12:11 PM, Kevin Risden wrote:
>> You can do this as a bulk transition to avoid emailing everyone of the
>> change. If you select "Tools" -> "Bulk change".
>> Kevin Risden
>> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
>>> Hi all,
>>>
>>> As I have suggested on a related thread[1] started by Stamatis, I am
>>> planning to close the JIRA tickets that are marked as status "RESOLVED" but
>>> bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
>>> and its fix version is provided but not one of our unreleased versions
>>> 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
>>> to be closed.
>>>
>>> Here is a link to the full list (currently 78 tickets in total):
>>>
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>>>
>>> I'll close them by the ascending order of JIRA ID respectively. If you
>>> used to participate in the discussion of any issue on the list, and you
>>> think it is too early to close, please feel free to reopen and add some
>>> follow-up comments.
>>>
>>> Thanks,
>>> Hongze
>>>
>>>
>>> [1]
>>> https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>>>
Re: Clean up JIRA tickets
Posted by Josh Elser <el...@apache.org>.
Yes, please check the "don't send emails" button in the future :)
Thanks for cleaning them up, Hongze!
On 4/29/19 12:11 PM, Kevin Risden wrote:
> You can do this as a bulk transition to avoid emailing everyone of the
> change. If you select "Tools" -> "Bulk change".
>
> Kevin Risden
>
>
> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
>
>> Hi all,
>>
>> As I have suggested on a related thread[1] started by Stamatis, I am
>> planning to close the JIRA tickets that are marked as status "RESOLVED" but
>> bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
>> and its fix version is provided but not one of our unreleased versions
>> 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
>> to be closed.
>>
>> Here is a link to the full list (currently 78 tickets in total):
>>
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>>
>> I'll close them by the ascending order of JIRA ID respectively. If you
>> used to participate in the discussion of any issue on the list, and you
>> think it is too early to close, please feel free to reopen and add some
>> follow-up comments.
>>
>> Thanks,
>> Hongze
>>
>>
>> [1]
>> https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>>
>
Re: Clean up JIRA tickets
Posted by Kevin Risden <co...@gmail.com>.
You can do this as a bulk transition to avoid emailing everyone of the
change. If you select "Tools" -> "Bulk change".
Kevin Risden
On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang <no...@126.com> wrote:
> Hi all,
>
> As I have suggested on a related thread[1] started by Stamatis, I am
> planning to close the JIRA tickets that are marked as status "RESOLVED" but
> bound with an earlier fix version. Say, if a ticket is marked "RESOLVED",
> and its fix version is provided but not one of our unreleased versions
> 1.20.0/1.21.0/avatica-1.15.0/avatica-go-4.0.0/avatica-go-5.0.0, it is going
> to be closed.
>
> Here is a link to the full list (currently 78 tickets in total):
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20not%20in%20(1.20.0%2C1.21.0%2Cavatica-1.15.0%2Cavatica-go-4.0.0%2Cavatica-go-5.0.0)
>
> I'll close them by the ascending order of JIRA ID respectively. If you
> used to participate in the discussion of any issue on the list, and you
> think it is too early to close, please feel free to reopen and add some
> follow-up comments.
>
> Thanks,
> Hongze
>
>
> [1]
> https://lists.apache.org/thread.html/03f1e1937892e2ccbb30b639219122c28ca3c389e10aa01ed2214ca1@%3Cdev.calcite.apache.org%3E
>