# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1593438027 -7200
# Node ID 987fbbc2b59e151ecf1ace0b1011674aaa00ff81
# Parent  06521ac2c14a35554822af9146ca68fc389b2dac
leaving bitbucket wrt. bug tracker

diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/contributing.rst
--- a/Sphinx/source/contributing.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/contributing.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -36,8 +36,8 @@
 * **Maintenance tasks**:
       
   - Report problems together with sample DICOM images and possible
-    workarounds on the `issue tracker
-    <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`_.
+    workarounds on the dedicated `issue tracker
+    <http://bugs.orthanc-server.com/>`_.
   - Package Orthanc and its associated plugins for more UNIX or
     GNU/Linux distributions (e.g. Ubuntu PPA, RHEL, CentOS, openSUSE...).
   - Share your maintenance scripts or sample code inside the "`Orthanc Contributed
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/developers/repositories.rst
--- a/Sphinx/source/developers/repositories.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/developers/repositories.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -237,7 +237,15 @@
 Issue tracker
 -------------
 
-This is work-in-progress. Orthanc will most probably move to the
-`Roundup issue tracker
-<https://en.wikipedia.org/wiki/Roundup_(issue_tracker)>`__ that is
-notably used by the Python community.
+The `official bug tracker <https://bugs.orthanc-server.com/>`__ of the
+Orthanc project runs thanks to `Bugzilla
+<https://en.wikipedia.org/wiki/Bugzilla>`__.
+
+We have done our best to automatically import most of the history
+from the old BitBucket bug tracker.
+
+Before posting any issue, make sure to carefully, completely read the
+:ref:`page about how to ask support <support>`. In particular, most
+issues should first be discussed on the dedicated `discussion group
+<https://groups.google.com/forum/#!forum/orthanc-users>`__ before
+introducing a bug report.
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/faq/licensing.rst
--- a/Sphinx/source/faq/licensing.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/faq/licensing.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -241,9 +241,8 @@
 
 Once the CLA onboarding process has succeeded, use `Mercurial
 <https://en.wikipedia.org/wiki/Mercurial>`__ to fork the official
-repository of interest from BitBucket. All the repositories are
-centralized on our `self-hosted Mercurial server
-<https://hg.orthanc-server.com/>`__.
+repository of interest. All the repositories are centralized on our
+`self-hosted Mercurial server <https://hg.orthanc-server.com/>`__.
 
 A :ref:`dedicated page <repositories>` explains how to submit
 :ref:`simple patches <hg-patch>` or :ref:`full branches <hg-bundle>`.
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/faq/scalability.rst
--- a/Sphinx/source/faq/scalability.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/faq/scalability.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -195,9 +195,9 @@
 respect, for which we are looking for funding from the
 industry. Some issues reported in our bug tracker call for this
 refactoring: `issue 83
-<https://bitbucket.org/sjodogne/orthanc/issues/83/>`__, `issue 121
-<https://bitbucket.org/sjodogne/orthanc/issues/121/>`__, `issue 151
-<https://bitbucket.org/sjodogne/orthanc/issues/151/>`__.
+<https://bugs.orthanc-server.com/show_bug.cgi?id=83>`__, `issue 121
+<https://bugs.orthanc-server.com/show_bug.cgi?id=121>`__, `issue 151
+<https://bugs.orthanc-server.com/show_bug.cgi?id=151>`__.
 
 
 Latency
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/plugins/dicomweb.rst
--- a/Sphinx/source/plugins/dicomweb.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/plugins/dicomweb.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -171,8 +171,8 @@
   area <orthanc-storage>`, which gives fully accurate results but
   requires all the individual instances to be read and parsed from the
   filesystem, leading to slow performance (cf. `issue 162
-  <https://bitbucket.org/sjodogne/orthanc/issues/162/dicomweb-metadata-resource-reads-all>`__).
-  This is the default mode.
+  <https://bugs.orthanc-server.com/show_bug.cgi?id=162>`__). This is
+  the default mode.
 
 * If ``MainDicomTags`` mode is used, the plugin will only report the
   main DICOM tags that are indexed by the Orthanc database. The DICOM
@@ -293,7 +293,7 @@
   ``ChunkedTransfers`` to ``true`` in Orthanc 1.5.7 and 1.5.8 utilizes
   one CPU at 100%, which results in very low throughput: This issue is
   resolved in Orthanc 1.6.0 (cf. `issue 156
-  <https://bitbucket.org/sjodogne/orthanc/issues/156/>`__ for full
+  <https://bugs.orthanc-server.com/show_bug.cgi?id=156>`__ for full
   explanation).
 
 * ``HasWadoRsUniversalTransferSyntax`` (new in DICOMweb 1.1) must be
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/plugins/postgresql.rst
--- a/Sphinx/source/plugins/postgresql.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/plugins/postgresql.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -251,8 +251,7 @@
 
 After some period of inactivity (users have reported 10 hours), you
 might `experience an error
-<https://bitbucket.org/sjodogne/orthanc/issues/15/postgresql-exceptions-after-time>`__
-such as::
+<https://bugs.orthanc-server.com/show_bug.cgi?id=15>`__ such as::
 
   E0220 03:20:51.562601 PluginsManager.cpp:163] Exception in database back-end: Error in PostgreSQL: server closed the connection unexpectedly.
   This probably means the server terminated abnormally before or while processing the request.
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/users/cookbook.rst
--- a/Sphinx/source/users/cookbook.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/users/cookbook.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -53,8 +53,9 @@
 to upload files to Orthanc through Orthanc Explorer with Chromium.
 
 **Important:** There is currently a `known issue
-<https://bitbucket.org/sjodogne/orthanc/issues/21/dicom-files-missing-after-uploading-with>`__
-that prevents Mozilla Firefox to correctly upload all DICOM files.
+<https://bugs.orthanc-server.com/show_bug.cgi?id=21>`__ that might
+prevent Mozilla Firefox to correctly upload all DICOM files if using
+drag-and-drop.
 
 
 Uploading through the DICOM protocol
diff -r 06521ac2c14a -r 987fbbc2b59e Sphinx/source/users/support.rst
--- a/Sphinx/source/users/support.rst	Sat Jun 06 16:34:40 2020 +0200
+++ b/Sphinx/source/users/support.rst	Mon Jun 29 15:40:27 2020 +0200
@@ -38,10 +38,10 @@
    <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
    contains our roadmap, as you might be requesting a feature that is
    currently pending in our backlog (i.e. not implemented yet).
-10. Have a look for the issue in the `official bug tracker
-    <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__
-    (click on the ``All`` button, as your issue might already been
-    solved).
+10. Look for similar issue in the `official bug tracker
+    <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to
+    select ``All`` in the ``Status`` field, as your issue might
+    already have been solved).
 
 
 Importantly, for all the features that are pending in the ``TODO``
@@ -101,6 +101,6 @@
 
 If you are **sure** that you are reporting a yet unknown bug, you can
 consider directly introducing a `bug report on our issue tracker
-<https://bitbucket.org/sjodogne/orthanc/issues/new>`__. Beware however
+<https://bugs.orthanc-server.com/enter_bug.cgi>`__. Beware however
 that your issue might be closed if too vague or if not reproducible.
 As a consequence, it is advised to first use the discussion forum.