Hi Konrad, On Tue, 2020-04-07 at 12:20 +0200, Konrad Windszus wrote: > Hi, > I asked in https://issues.apache.org/jira/browse/INFRA-19695 < > https://issues.apache.org/jira/browse/INFRA-19695> about enabling a > Github JIRA integration so that commits automatically become visible > in the related JIRA ticket. > The standard Atlassian JIRA Github integration cannot be used but > instead the agent svn2jira can be enabled ( > https://fisheye.apache.org/browse/~br=gm%402fselfserve-cli-tools/Infrastructure-puppet/modules/svngit2jira/files/app/svngit2jira.py?r=e78ad4c145e97354151021c85eaaa17dbd54b773 > < > https://fisheye.apache.org/browse/~br=gm@2fselfserve-cli-tools/Infrastructure-puppet/modules/svngit2jira/files/app/svngit2jira.py?r=e78ad4c145e97354151021c85eaaa17dbd54b773> > ;) > which will either > a) write the commit links to comments or > b) just write them in the work log of the JIRA > > > Tracking inside the development panel is not possible at the moment. > > Should I request to enable svn2jira for all Sling repositories? > Which option do you prefer (a or b)?
At some point I asked for the GH comments to be turned off, since they were posting full diffs as Jira comments, which was very noisy. https://issues.apache.org/jira/browse/INFRA-16219 Currently we have PRs written in the worklog for some (most?) modules. I don't have a strong opinion, as long as we don't get flood of Jira comments again. Workflog is fine. I think comments about PR open/closed/merged are also fine and useful. Thanks, Robert > > You see examples of a0 in > https://issues.apache.org/jira/browse/INFRA-18763?focusedCommentId=16903027&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16903027 > and examples of b) in > https://issues.apache.org/jira/browse/INFRA-19695?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aworklog-tabpanel > < > https://issues.apache.org/jira/browse/INFRA-19695?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel > > > > Thanks for your input, > Konrad
