+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 <zabe...@gmail.com> 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
