View source for Documentation/4.3/Report a problem

<noinclude>{{documentation/versioncheck}}</noinclude>


=User Feedback=

*I have a question about how to use Slicer for a particular task
** Look at our [[Documentation/UserTraining|portfolio of training materials]] and make a google search to see, if the question has been discussed in the mailinglists.
** I am still unclear about what to do. In this case, sign up for the slicer user mailing list: [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-user Sign-up]
*Something is not working as it should or I would like to request a feature.
** File a bug report in the issues [http://na-mic.org/Mantis/bug_report_page.php tracker] (you need to register first). It is important to provide enough specific information so that a software developer can duplicate the problem. [[Documentation/{{documentation/version}}/Report_a_problem#Workflow_for_Handling_Bugs_and_Feature_Requests_in_Slicer|See below]] for more details.
* I would like to let the Slicer community know, how Slicer helped me in my research.
**Please send us the citation for your paper.
**Background: funding for Slicer is provided through competitive mechanisms to a large extent by the US government and to a lesser extend through funding from other governments. The justification of for those resources is that Slicer enables scientific work. Knowing about scientific publications enabled by Slicer is a critical step in this process. Given the international nature of the Slicer community, the nationality of the scientists is not important. Every good paper counts.
* I would like to give feedback on my experience with Slicer.
**Share your story using the Feedback link accessible from the Slicer Welcome module

==Workflow for Handling Bugs and Feature Requests in Slicer==
The following instructions describe the recommended workflow to report a problem related to Slicer application. The issue flows from top left to bottom left following the arrows. Issues are bug reports, feature requests and similiar items. A data base with a web interface is at the core of this software engineering methodology.

* 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}}