Thanks Suresh for the earlier reply. Hi Albert,
HDFS-7285 is created as the so called umbrella jira for the project, and the subtasks are created incrementally afterwards when the subtasks are defined (let's call this subtask mechanism). For jiras created in any order without using the subtask mechanism, we can link them together via the link mechanism. When creating the link, we can assign an attribute to the link such as "is related to", "incorporates" etc. Particularly, HDFS-7343 is created and linked to HDFS-7285 as "is related to" upon discussion in HDFS-7285. My thinking is, HDFS-7343 could have been created as a subtask of HDFS-7285, but since HDFS-7343 is kind of general for different areas including HDFS-7285 to utilize, so it's reasonable to use "is related to". Or probably we can make it "is required by" HDFS-7285, but I'm not so sure. About like HDFS-7285 incorporates HDFS-7545, these two jiras can be created separately. My understanding is, if HDFS-7545 is not created as a subtask of HDFS-7285, if we want to still make them a subtask relationship, the "incorporates" link serve this purpose. Another thing I noticed was, when creating a subtask of a HDFS jira, the subtask will be HDFS jira (the subtask will be of the same type of parent task). It seems one can not create a HDFS jira subtask of type HSDOOP. This is when I think "incorporates" link come into plan. Other folks please correct me if I'm wrong. BTW, I think it'd be nice for the display of subtasks in a jira to show both the jira id and the summary, currently only the summary is shown. Hope that helps. Thanks. --Yongjun On Sat, Feb 28, 2015 at 10:38 AM, C. Albert Thompson < gm...@c.albert-thompson.com> wrote: > Suresh, > > Thank you for the response. That is helpful for seeing parent child > relationship. HDFS-7285 is a task and has 51 subtasks. > > I want to learn more about relationships like HDFS-7285 incorporates > HDFS-7545. Were these two created in parallel? > Or when I see a HDFS-7285 is related to HDFS-7343 J. Why is the > relationship? How is that decision made to choose a relationship? > > > -- > Cheers, > -C. Albert Thompson > > On Fri, Feb 27, 2015 at 9:14 PM, Suresh Srinivas <sur...@hortonworks.com> > wrote: > > > Albert, > > > > Jira has a way to create subtasks. This is not captured through linking > of > > two jiras but as parent child relationship. Example, see - > > https://issues.apache.org/jira/plugins/servlet/mobile#issue/HDFS-7285 > and > > its sub-tasks. > > > > Regards, > > Suresh > > > > Sent from phone > > > > > > > > > > On Fri, Feb 27, 2015 at 4:33 PM -0800, "C Albert Thompson" < > > gm...@c.albert-thompson.com<mailto:gm...@c.albert-thompson.com>> wrote: > > > > I am a researcher at UBC I am trying to understand relationships between > > the issues in HADOOP Jira issue repository. > > There are 20 possible relationships shown below. I want to understand for > > HADOOP what is the hierarchy of issues. For example, if you are given an > > issue and you want to break it down into sub-issues would you label the > > sub-issues with “blocks" or "is blocked by"? Or are the possible > > relationships parallel? > > > > In the following possible relationships found in HADOOP. I consider > > > > A 'incorporates' B > > C 'relates to’ D > > E 'requires' F > > G 'blocks' H > > I 'contains' J > > K 'breaks' L > > M 'depends upon' N > > O 'supercedes’ P > > Q 'duplicates' R > > S 'is a clone of' T > > > > > > Here is the same list but with the reverse of the previous list. > > > > B 'is part of' A > > D 'is related to' C > > F 'is required by' E > > H 'is blocked by' G > > J 'Is contained by' I > > L 'is broken by' K > > N 'is depended upon by' M > > P 'is superceded by' O > > R 'is duplicated by' Q > > T 'is cloned as’ S > > > > > > For A-S Wich would be the issue? and which ones would be considered the > > sub-issues? > > >
