[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048019#comment-18048019 ] Zhen Chen commented on CALCITE-7282: Yes, I've looked into it carefully, and it's really not necessary. If we want to achieve this Jira requirement, it seems the only way is through a GitHub Action. I tried the official Jira plugins, but they don't seem to work. My first PR attempted to directly call the Jira API, but that felt too verbose and difficult for others to understand. It seems this issue will be shelved for a long time. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048012#comment-18048012 ] Stamatis Zampetakis commented on CALCITE-7282: -- The "comment" and "worklog" [options|https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#jira-notification-options] will add extra notifications in the Jira ticket that I feel we don't need. The link to the GitHub PR we have it already in the ticket so there is no need to have additional comments everytime it changes status. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047960#comment-18047960 ] Zhen Chen commented on CALCITE-7282: It needs to be clarified that this modification only adds comments to Jira and does not change Jira's status. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047902#comment-18047902 ] Zhen Chen commented on CALCITE-7282: I have received the response; I only need to add a "comment". Do you agree? If you agree, I will submit a PR to complete it. If everything goes as expected, this will significantly reduce the workload for the reviewers. The reply received is as follows: Your .asf.yaml is missing the 'comment' option - see https://github.com/apache/hadoop/blob/trunk/.asf.yaml#L27 I believe it should work as you intend after that is added > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046889#comment-18046889 ] Zhen Chen commented on CALCITE-7282: I think this is a good suggestion. I submitted a Jira INFRA-27519 to see if anyone can provide guidance. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036742#comment-18036742 ] Zhen Chen commented on CALCITE-7282: I found that in the Hadoop Jira like HDFS-17847, there's an ASF GitHub Bot that can synchronize GitHub operations to JIRA. I think I might not have sufficient permissions to see higher-level content in the Calcite repository and JIRA. Also, I noticed that the Hadoop repository doesn't use GitHub Actions. So GitHub Actions might not be a good solution. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > Labels: pull-request-available > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036649#comment-18036649 ] Zhen Chen commented on CALCITE-7282: I searched for INFRA but couldn't find any related practices—perhaps I'm not very good at using JIRA's search function. If you think the action approach is acceptable, I will submit a PR. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036573#comment-18036573 ] Zhen Chen commented on CALCITE-7282: This is my first time writing a GitHub Action. If the current implementation is inadequate or does not yet meet the requirements, please let me know. I will continue to refine it. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Assignee: Zhen Chen >Priority: Minor > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[
https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036529#comment-18036529
]
Zhen Chen commented on CALCITE-7282:
I have created an
[action|https://github.com/xiedeyantu/calcite-fusion/blob/main/.github/workflows/resolve-jira-on-merge.yml]
in my personal repository to automatically update the status of CALCITE issues
when pull requests are merged. The current implementation extracts issue keys
by matching patterns like {{{}[CALCITE-]{}}}in PR titles and then calls
the Jira API to transition the issue status. You can see the result on
CALCITE-7283.
If this approach is deemed useful, I recommend applying for a dedicated Jira
account with write permissions to handle these automated transitions.
Currently, I am using my personal token for testing
> Could a bot be used to resolve JIRA issues?
> ---
>
> Key: CALCITE-7282
> URL: https://issues.apache.org/jira/browse/CALCITE-7282
> Project: Calcite
> Issue Type: Improvement
>Reporter: Mihai Budiu
>Assignee: Zhen Chen
>Priority: Minor
>
> Today committers have to do some tedious manual work to list the commit which
> resolves an issue.
> Perhaps this work could be automated by adding a bit of information in the
> PR, e.g.
> Fixes: [CALCITE-]
> This would require a bot that monitors github and updates Jira tickets.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CALCITE-7282) Could a bot be used to resolve JIRA issues?
[ https://issues.apache.org/jira/browse/CALCITE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036347#comment-18036347 ] Stamatis Zampetakis commented on CALCITE-7282: -- You can search in the INFRA project to see if something similar was done for another project. > Could a bot be used to resolve JIRA issues? > --- > > Key: CALCITE-7282 > URL: https://issues.apache.org/jira/browse/CALCITE-7282 > Project: Calcite > Issue Type: Improvement >Reporter: Mihai Budiu >Priority: Minor > > Today committers have to do some tedious manual work to list the commit which > resolves an issue. > Perhaps this work could be automated by adding a bit of information in the > PR, e.g. > Fixes: [CALCITE-] > This would require a bot that monitors github and updates Jira tickets. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
