You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2025/05/27 11:04:00 UTC

[jira] [Commented] (CALCITE-7040) Expect Jira tickets to be included in each PR description

    [ https://issues.apache.org/jira/browse/CALCITE-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954293#comment-17954293 ] 

Stamatis Zampetakis commented on CALCITE-7040:
----------------------------------------------

Hey [~jensen] , I don't completely understand your proposal can you please elaborate a bit more and/or give some examples of what you have in mind.

> Expect Jira tickets to be included in each PR description
> ---------------------------------------------------------
>
>                 Key: CALCITE-7040
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7040
>             Project: Calcite
>          Issue Type: Wish
>            Reporter: Zhen Chen
>            Priority: Major
>
> As discussed before, Calcite is based on Jira for solution discussion and GitHub for code implementation. Currently, submitting a PR will automatically link to Jira, but the Jira link will not be automatically included in the PR. We must open Jira again to find the corresponding number. Is it possible to include the Jira link in each PR by default, so that reviewers can check back and forth to avoid omissions?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)