You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Stamatis Zampetakis <za...@gmail.com> on 2022/10/14 09:04:52 UTC
Consider using bi-directional links in JIRA
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
HIVE-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 (HIVE-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
Re: Consider using bi-directional links in JIRA
Posted by Alessandro Solimando <al...@gmail.com>.
+1 too for bringing up this discussion, navigating through related issues
is very important.
Benchao: in general the most important is to put the link (even just
"relates to" or "duplicates" as Julian said), we can defer more complex
relationships to the description or comments.
Other ones I use (although rarely) are "blocks" and "split from".
For case 1/2/4 I would use "relates", for 3 "split from", but I guess that
there are no precise rules around that.
Best regards,
Alessandro
On Sat 15 Oct 2022, 05:41 Benchao Li, <li...@apache.org> wrote:
> 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 <jh...@gmail.com> 于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 <za...@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
> >
> >
>
> --
>
> Best,
> Benchao Li
>
Re: Consider using bi-directional links in JIRA
Posted by Benchao Li <li...@apache.org>.
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 <jh...@gmail.com> 于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 <za...@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
>
>
--
Best,
Benchao Li
Re: Consider using bi-directional links in JIRA
Posted by Julian Hyde <jh...@gmail.com>.
+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 <za...@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
Fwd: Consider using bi-directional links in JIRA
Posted by Stamatis Zampetakis <za...@gmail.com>.
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
Re: Consider using bi-directional links in JIRA
Posted by Stamatis Zampetakis <za...@gmail.com>.
I added a few sentences about this in JIRA Guidelines [1].
Best,
Stamatis
[1] https://cwiki.apache.org/confluence/display/Hive/HowToContribute
On Thu, Oct 20, 2022 at 4:56 AM Naveen Gangam <ng...@cloudera.com> wrote:
> +1. I find this very useful to know the dependencies/relationships. Thank
> you for bringing this up.
>
> On Fri, Oct 14, 2022 at 5:06 AM Stamatis Zampetakis <za...@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
>> HIVE-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 (HIVE-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
>>
>
Re: Consider using bi-directional links in JIRA
Posted by Stamatis Zampetakis <za...@gmail.com>.
I added a few sentences about this in JIRA Guidelines [1].
Best,
Stamatis
[1] https://cwiki.apache.org/confluence/display/Hive/HowToContribute
On Thu, Oct 20, 2022 at 4:56 AM Naveen Gangam <ng...@cloudera.com> wrote:
> +1. I find this very useful to know the dependencies/relationships. Thank
> you for bringing this up.
>
> On Fri, Oct 14, 2022 at 5:06 AM Stamatis Zampetakis <za...@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
>> HIVE-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 (HIVE-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
>>
>
Re: Consider using bi-directional links in JIRA
Posted by Naveen Gangam <ng...@cloudera.com.INVALID>.
+1. I find this very useful to know the dependencies/relationships. Thank
you for bringing this up.
On Fri, Oct 14, 2022 at 5:06 AM Stamatis Zampetakis <za...@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
> HIVE-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 (HIVE-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
>
Re: Consider using bi-directional links in JIRA
Posted by Naveen Gangam <ng...@cloudera.com>.
+1. I find this very useful to know the dependencies/relationships. Thank
you for bringing this up.
On Fri, Oct 14, 2022 at 5:06 AM Stamatis Zampetakis <za...@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
> HIVE-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 (HIVE-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
>