[
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-<number>]{}}}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-XXXX]
> This would require a bot that monitors github and updates Jira tickets.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
