Any suggestions to this Topic? I read the Guidelines for that: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 but no proposals for Sub-tasks.
Ok here is my proposal, I think it depends on the feature but if you have an amount of small Sub Tasks it could be separate commits for each Sub Task in one PR. If you have a lot of work, it would make much more sense to have one PR for each Sub Task. In my Situation, of Course both are 2 new Features/improvements, which could be 2 separate stories but both are a bit connected to each other, because I want to use a shortcut to open the Thing and type into a search field. Do you have any other suggestions for that? I’m also fine to split my ticket into 2 tickets instead of having 2 sub Tasks of 1 ticket. Cheers Chris Von: Christian Lenz Gesendet: Dienstag, 18. September 2018 14:25 An: [email protected] Betreff: Ticket, Sub-Tasks and PRs Dear Devs, I created a new ticket, for a new feature, which I want to implement: https://issues.apache.org/jira/browse/NETBEANS-1262 This ticket Needs 2 implementations. One Action to create a shortcut (One Sub-Task) and create a new searchfield to filter the list inside the Show opened documents list popup (Second Sub-Task). First I want to know, whether it is correct to create for each Little feature, which depends on the Overall feature, a sub ticket or not and second how should I handle the PR? Should I create a new branch (In my fork or directly in the incubator repo?) for each Sub ticket or a PR for the Ticket itself and not for the Sub Tasks? Cheers Chris
