|
|
(19 intermediate revisions by 5 users not shown) |
Line 1: |
Line 1: |
− | <noinclude>{{documentation/versioncheck}}</noinclude>
| + | {{documentation/banner |
− | The following instructions describes the recommended workflow to report a problem related to Slicer application.
| + | | text = [https://slicer.readthedocs.io/en/latest/user_guide/get_help.html#i-want-to-report-a-problem This page has been moved to read-the-docs.] |
− | | + | | background-color = 8FBC8F }} |
− | * 1. [http://na-mic.org/Mantis/signup_page.php Register] on the issue tracker
| |
− | | |
− | * 2. [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel Sign-up] on the developers mailing list
| |
− | | |
− | * 3. Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. For example, see issue [http://na-mic.org/Mantis/view.php?id=1906 #1906]
| |
− | | |
− | * 4. Optionally, if you would like to share dataset >= 2MB, you should consider uploading them on our dedicated server. See [[Documentation/{{documentation/version}}/Report_a_problem/UploadData|How to share and associate data with an issue]]
| |
− | | |
− | * 5. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported bug. Title of the email should start with <code>[BUG 1234] Title of the bug</code>
| |
− | | |
− | {{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}}
| |