Thanks Stamatis for the reminder. I'm also +1 for it. I agree that bi-directional links is helpful and important. But in which kind of cases should we use it and to use what kind of the link sometimes is not that clear.
Julian's reply answers second question, and it is great to not worry about the link types too much. For the first question, I would give a few examples: 1. CALCITE-5326, CALCITE-5299 and CALCITE-5265, these three issues are independent, but similar, they all talks about "redundant parentheses while unparsing" 2. CALCITE-5310 is a issue which mentioned firstly in CALCITE-5127, but a it's separate issue 3. CALCITE-5304 is a follow-up issue of CALCITE-5127, which is created in the process of code review 4. During CALCITE-4982's discussion, we referenced CALCITE-5315 and CALCITE-2450 What I would like to ask is that is there any rule or guidance to draw a line for linking issues? Julian Hyde <[email protected]> 于2022年10月15日周六 02:48写道： > +1 > > Thanks for this reminder, Stamatis. Bi-directional links help us navigate > around the graph of related issues, identify duplicate bugs, do forensics, > and also to break down the roadmap (aspirational features) into smaller, > incremental tasks. I use them a lot. > > Our Jira instance is an amazing knowledge-base of issues, past and future > work, and maintaining bidirectional links maximizes its value. > > Don’t worry too much about the link type. “Duplicate” and “related” are > about the only ones I use. > > Julian > > > > On Oct 14, 2022, at 2:06 AM, Stamatis Zampetakis <[email protected]> > wrote: > > > > Hi all, > > > > This is a small tip/reminder for everyone using JIRA. > > > > It is very common and convenient to refer to other tickets by adding the > > CALCITE-XXXXX pattern in summary, description, and comments. > > > > The pattern allows someone to navigate quickly to an older JIRA from the > > current one but not the other way around. > > > > Ideally, along with the mention (CALCITE-XXXXX) pattern, it helps to add > an > > explicit link (relates to, causes, depends upon, etc.) so that the > > relationship between tickets is visible from both ends. > > > > This is extremely useful when we are reporting a regression/breaking > change > > from a past commit but in other cases as well. > > > > Best, > > Stamatis > > -- Best, Benchao Li
