Hi Pierre, All,
Actually I mostly use 3 types of parent-children issues relations:
1. Subtasks
2. Part of (and "is part of")
3. Child of (and "is a parent of)"
The 1st was available with 1st versions of Jira we used. The 2nd came after and
the later is even more recent.
I use subtasks when the children issues are closely related to the parent one, like a section in a document to image it. I think a subtask can only be
part of a parent issue (did not check).
I use indifferently "Part of" and "Child of". Maybe they can be related to several parents unlike subtasks? I think they were successively put in by
the Jira ASF admins, not sure how to differentiate them and even from subtasks.
So I come to the same conclusion than here:
https://stackoverflow.com/questions/20357372/issue-links-meaning-in-jira
There is also (and reversed relations, like "Is contained by")
* Contains
* Incorporates
* Is required by
* Is depended upon by
For the 2 last I think meanings are more clear, not sure for the 2 1st :D. They
could be part of the list of 3 above...
I don't think we need to clearly define the differences since it might still evolve with Jira ASF admins creativity (mostly requests from Jira users),
as long as we understand what we are doing.
My 2cts
Jacques
Le 17/05/2019 à 09:13, Pierre Smits a écrit :
Hi All,
Some contributors have suggested (in comments in this ML on the above
ticket) that we make more use of the ParentTicket-ChildTicket mechanism
(meaning that BugFix and Improvement tickets are converted to SubTask
tickets) in JIRA to enable parties involved to get a better overview of
what is related.
I seem to remember that this discussion has come before (as side comments
to tickets and in other threads), but can't easily reference a single one
from the past. And IIRW there are both proponents and opponents for the
concept.
What are your thoughts on this? And, can we get a consensus on the subject
and register that in one of our BestPractice pages?
Best regards,
Pierre Smits
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer
On Fri, May 17, 2019 at 8:29 AM Suraj Khurana <[email protected]>
wrote:
Hello,
I am inclined with Aditya's thought here.
Furthermore, a parent ticket works well for task and new feature tickets.
And not that well for bug fix and improvement tickets.
IMO, it does. [1]
As a reviewer, I think of all the tickets are bundled together inside a
parent ticket, than it would be better. Yes, there are other ways, but if
we can arrange tickets properly, it is considered a best practice to do so.
[1] : https://issues.apache.org/jira/browse/OFBIZ-7649 |
<https://issues.apache.org/jira/browse/OFBIZ-7649>
https://issues.apache.org/jira/browse/OFBIZ-8408
--
Best Regards,
Suraj Khurana
Technical Consultant
On Fri, May 17, 2019 at 12:40 AM Pierre Smits <[email protected]>
wrote:
Hi Aditya, All,
IMO, there are already to many tickets not worked on, but being managed.
And I don't see much progress initiated by the assignees of those tickets
to get the work of the underlying tasks completed. While parent tickets
(and sub tasks) work well for other parties with a more hierarchical and
contractually controlled structure, it does not work that well for an
organisation like the ASF (and projects under its umbrella) where
activities of contributors can't be dictated, nor managed by the assignee
of the parent ticket.
Furthermore, a parent ticket works well for task and new feature tickets.
And not that well for bug fix and improvement tickets.
If you (and others) want to keep track of progress, I believe, there are
ample ways to do that. JIRA provides plenty of tools to get an overview
of
whatever. One of such is
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12310603
and I feel confident that anyone can create a good filter on OFBiz
tickets
that will deliver on specific needs.
An other way to track progress regarding OFBiz Business Intelligence (aka
the BI component) is through the wiki pages associated with the subject,
see e.g.
https://cwiki.apache.org/confluence/display/OFBIZ/Business+Intelligence
Best regards,
Pierre Smits
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without
privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer
On Thu, May 16, 2019 at 2:45 PM Aditya Sharma <[email protected]>
wrote:
Hi Pierre,
It seems work is related to Business Intelligence[1] work. Thanks for
your
efforts in this direction.
I would suggest that it would be much better if you could have a parent
ticket for all these tasks that define the plan and purpose. It would
quite
easy to track the progress if the tickets are grouped together.
1.
https://cwiki.apache.org/confluence/display/OFBIZ/Business+Intelligence
On Thu, May 16, 2019 at 4:12 PM Pierre Smits (JIRA) <[email protected]>
wrote:
[
https://issues.apache.org/jira/browse/OFBIZ-11031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-11031:
---------------------------------
Labels: Fact SalesOrder SalesOrderItemFact birt dwh (was: dwh)
Improve SalesOrderItemFact table
--------------------------------
Key: OFBIZ-11031
URL:
https://issues.apache.org/jira/browse/OFBIZ-11031
Project: OFBiz
Issue Type: Improvement
Components: bi
Affects Versions: Trunk, Release Branch 17.12, Release Branch
18.12
Reporter: Pierre Smits
Priority: Major
Labels: Fact, SalesOrder, SalesOrderItemFact, birt,
dwh
Improve the SalesOrderFactTable to include additional dimensions
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
