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 <pierresm...@apache.org>
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 <adityasha...@apache.org>
> 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) <j...@apache.org>
> > 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)
> > >
> >
>

Reply via email to