<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On Dec 31, 2015, at 12:03 PM, Joe Groff via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 31, 2015, at 11:47 AM, Keith Smiley via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Would it be worthwhile for the swift team if those of us who have created many swift related radars to copy them over to <a href="http://bugs.swift.org/" class="">bugs.swift.org</a>?</div></div></blockquote><br class=""></div><div>Definitely. If you can spare the extra effort, we'd appreciate cross references between the public and Radar bugs on Jira and Radar too.</div></div></blockquote><br><div>+1</div><div><br></div><div>For the Swift Team at Apple, we're looking into what workflows will work best for tracking issues and managing our engineering work in the two bug databases. We'd like to keep issues in JIRA as much as possible, but we'll also being using Radar heavily as we use it for managing our engineering work and tracking the resolution of issues/fixes into Apple's shipping tools. Cross-referencing between the two will be invaluable, and we'll likely invest some effort on our side to having some tooling to help bridge at least from JIRA issues to Radar so we can keep more of the core issue tracking in JIRA.</div></body></html>