Difference between revisions of "Documentation/4.3/Report a problem"
From Slicer Wiki
(Nightly -> 4.3) |
|||
| Line 1: | Line 1: | ||
<noinclude>{{documentation/versioncheck}}</noinclude> | <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]]. | ||
| + | |||
| + | |||
The following instructions describes the recommended workflow to report a problem related to Slicer application. | The following instructions describes the recommended workflow to report a problem related to Slicer application. | ||
Revision as of 08:35, 29 September 2013
Home < Documentation < 4.3 < Report a problem
|
For the latest Slicer documentation, visit the read-the-docs. |
User Feedback
- I have a question about how to use Slicer for a particular task
- Look at our portfolio of training materials.
The following instructions describes the recommended workflow to report a problem related to Slicer application.
- 1. Register on the issue tracker
- 2. Sign-up on the developers mailing list
- 4. Optionally, if you would like to share dataset >= 2MB, you should consider uploading them on our dedicated server. See How to share and associate data with an issue
- 5. Send an email on the slicer-developers list pointing to the reported bug. Title of the email should start with
[BUG 1234] Title of the bug
The following diagram illustrates Slicer issue workflow:
Source: Adapted from http://www.warelab.org/blog/?p=24
