So the INCORPORATED ISSUE is taged on all the sub or related tasks? on related task how do you determine which one should be INCORPORATED ISSUE. Like to help were I can on the ones I submit
[EMAIL PROTECTED] sent the following on 12/20/2007 11:19 AM: > Yes, Adrian I move the discussion on dev mailing list. > I'm sorry but was not my intention to made confusion on JIRA issues but > instead remove confusion from JIRA issues. > So I tried to start reorganization of JIRA issues on the following points: > > 1) assign to all the issues one or more components to understand where more > bug/improve are present (done). > > 2) for the INCORPORATED ISSUE (issue that contains link to single issue) I > would like to switch those to the new fictitious component and so I have > started to move those issues. > Doing this second step we will have a real view on which components have more > issues and need more help. > Some current INCORPORATED ISSUE has now all the linked issues closed but the > main issue has been not yet closed. > > 3) at the moment committer cannot understand easily which issue has already > patch attached to it and issue that have patch review and ready to be > committed. > So it's a very big problem for a new committer like me understand where I can > help like committer or like contributor. > I ask if we can add also a new state patch available and patch tested or > ready to be committed. > > So doing those and others chages can help and speed up in resolution and > contribution by committer/developer. > > I would like to receive some feedbacks otherwise I'm thinking that normally > people accept my proposals. > > Thanks in advance > Marco > > > ------- > [ > https://issues.apache.org/jira/browse/OFBIZ-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553492 > ] > > Marco Risaliti commented on OFBIZ-1151: > --------------------------------------- > > Also I like this workaround to see how many INCORPORATING ISSUE are active. > Before switch the others INCORPORATING ISSUE to this new fictitious > components I will wait some other feedback from others. > > Thanks > Marco > > ------- > > Marco, > > Perhaps you should discuss these changes on the dev mailing list before > changing them. > > -Adrian > > > >
