Mercurial > hg > orthanc-book

comparison Sphinx/source/users/support.rst @ 445:987fbbc2b59e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
leaving bitbucket wrt. bug tracker
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 29 Jun 2020 15:40:27 +0200
parents deee9da91633
children 74fc0203d882
comparison
equal deleted inserted replaced
444:06521ac2c14a 445:987fbbc2b59e
36 official release). 36 official release).
37 9. Carefully read the `TODO file 37 9. Carefully read the `TODO file
38 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that 38 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
39 contains our roadmap, as you might be requesting a feature that is 39 contains our roadmap, as you might be requesting a feature that is
40 currently pending in our backlog (i.e. not implemented yet). 40 currently pending in our backlog (i.e. not implemented yet).
41 10. Have a look for the issue in the `official bug tracker 41 10. Look for similar issue in the `official bug tracker
42 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__ 42 <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to
43 (click on the ``All`` button, as your issue might already been 43 select ``All`` in the ``Status`` field, as your issue might
44 solved). 44 already have been solved).
45 45
46 46
47 Importantly, for all the features that are pending in the ``TODO`` 47 Importantly, for all the features that are pending in the ``TODO``
48 file, if you are a company, please consider `buying professional 48 file, if you are a company, please consider `buying professional
49 services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order 49 services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order
99 Using the bug tracker 99 Using the bug tracker
100 --------------------- 100 ---------------------
101 101
102 If you are **sure** that you are reporting a yet unknown bug, you can 102 If you are **sure** that you are reporting a yet unknown bug, you can
103 consider directly introducing a `bug report on our issue tracker 103 consider directly introducing a `bug report on our issue tracker
104 <https://bitbucket.org/sjodogne/orthanc/issues/new>`__. Beware however 104 <https://bugs.orthanc-server.com/enter_bug.cgi>`__. Beware however
105 that your issue might be closed if too vague or if not reproducible. 105 that your issue might be closed if too vague or if not reproducible.
106 As a consequence, it is advised to first use the discussion forum. 106 As a consequence, it is advised to first use the discussion forum.