Yes, I was thinking on scmchangelog. With "excludeSubtasks" set and JIRA as issue tracker, for commits with issue id provided scmchangelog could obtain issue details, check if the issue is a subtask, and based on that decide whether to include issue in or exclude issue from the report. Commits without issue id can be excluded in this case, or even better another filter configuration option (e.g. new "excludeNonIssues" attribute of filter element) should be provided that would allow user to specify desired behavior. After applying these filters, regular already present filter option (if not empty) should be applied. These are all nice-to-haves.
Regards, Stevo. On Tue, Feb 10, 2009 at 9:34 AM, Rémy Sanlaville <remy.sanlavi...@gmail.com>wrote: > > > > Congrats, keep up the good work! > > > Thanks Stevo. We hope that our plugin > > > > One new feature suggestion - support for filtering subtasks (at least > when > > jira is issue tracker), e.g. through optional "excludeSubtasks" attribute > > of > > "filter" configuration element. > > > Are you sure that it is for our plugin and not for the > maven-changes-plugin. > In fact, with our plugin, you just have to not add the subtasks id in the > SCM comment. > > Regards, > > Rémy >
