ReSharper Issue Tracker, powered by JetBrains YouTrack, is a place where you can submit bug reports or feature requests.
To open ReSharper issue tracker, go to http://youtrack.jetbrains.net/issues/RSRP. Note that you will have to register in order to create requests (you can use your OpenID for a quick start). You can browse existing requests anonymously. You are welcome to submit feature requests and bug reports, but please first read the instructions below.
How to submit a request
You need to remember 3 simple rules:
- Please submit only one issue per request. It is extremely difficult to process composite requests, especially when different issues lay under responsibilities of different developers.
- If you have only a vague idea for a feature, please discuss it in ReSharper EAP newsgroup news://news.jetbrains.com/jetbrains.resharper.eap before submitting.
- Please try to search for duplicates before posting. This is how you search for requests in YouTrack. Developers need enough time to actually fix bugs or implement new features, don't they?
Thanks for understanding.
To get started with posting a request, just click New Issue in the upper menu bar, or press Alt+Ins. You will be asked to specify project and type of the request. Be sure to specify ReSharper in the top drop-down list. Use two text boxes two enter summary and description of your request:
- Summary: One-line description of a bug/feature. Try to make it short, but informative (we know, it is sometimes tricky). 'Bug in rename' is a bad summary. 'Renaming field creates conflict with local variable' is much better.
- Description: Longer description of a bug/feature. If you submit a bug, try to provide as much info as possible. Small code snippet to reproduce a problem is the best. If you submit a feature, it is a good idea to suggest some use cases. If you're submitting a bug report, please specify which ReSharper build it affects.
You can also attach additional files to your request (screenshots or some test cases). Use the Attach drop-down menu above the Summary text box for different attachment options.
Using the second button in the row under the Description text box, select one of the following types for your request:
- Feature - you are asking about new functionality or extending functionality of existing feature.
- Bug - you've found that existing feature doesn't work as you expect it to work, malfunctioning or doesn't work where you expect it to work. This is selected by default.
- Exception - you've encountered the Exception dialog box while working with ReSharper, but automatic submitting feature didn't work. Please include stacktrace.
- Cosmetics - you've encountered a spelling error, ugly graphics or any other aesthetic issue.
- Performance Problem - you perceive ReSharper works slowly, eats too much memory or makes Visual Studio's features run slower than usual.
- Usability Problem - you've found that a particular feature is hard to use or understand, or you feel that you're taking unneeded repetetive actions to achieve some result, or you think that interaction with user for some feature can be improved.
Be aware that when your request is processed its type may change (e.g. you think that some functionality is missing, while it has been already designed and implemented, but it just does not work - and your feature request becomes a bug report).
Click Submit or press Ctrl+Enter to submit your request.
Note that you don't need to set other request attributes such as priority, subsystem etc. - these are set by ReSharper team members when they receive your request.
What happens afterwards
After you submitted a request, it obtains a special state, namely Submitted. It means that the request has not been processed yet by the development team and awaits a decision on its further state.
When the request is processed it can be assigned one of the following states:
Open: we accept the request to be reasonable. You will see what version it is planned for (if any) and what priority is assigned to it.
Fixed: the request has been fixed/implemented. You will see the build number it is fixed in.
Duplicate: there is already a similar request. You will see the link to the request it is duplicating.
Incomplete: we agree there is a problem, but we cannot reproduce it and we (usually desperately) need more additional info. If request is assigned such a state, we will often give you some hints as to what data might help us.
Can't Reproduce: we cannot reproduce the problem. You will see the build number we have tried to reproduce it in. This usually means that either the problem was somehow fixed in course of other code changes, or we think there was just a mistake or misunderstanding.
To Be Discussed: we need to discuss whether and how this feature should be implemented, or whether this bug is really a bug. Everyone is welcome to participate in such discussions.
Won't Fix: we are not going to implement this feature or this is not a bug. Usually we will post an explanation.
Obsolete: the request is no longer applicable. This usually happens when the corresponding functionality has been changed dramatically since request submission.
Discuss an issue
Each YouTrack request can be commented. As a submitter, you will recieve e-mail notifications when someone comments it, or when an important change to the state of the request occur.
You can also start recieving notifications for any particular request you are interested in, by clicking the binocular icon ("Watch issue") under issue ID. To stop recieving notifications for an issue, click this icon once again.
When we open a request, we usually assign some priority to it. Please note that requests are not neccessarily going to be fixed in priority order. We use priorities mainly for our internal planning, and they are subject to change in the course of development.
Voting lets you express your preferences and opinions in "quantative" manner and gives us a hint of what is important to our users, but it is by far not the main factor in our planning. You can cast a vote against a feature you like or a bug report that you feel is important to you. To vote for an issue, click the icon displaying the current number of votes ("Vote for issue") under issue ID. If you changed you mind, you can "unvote" by clicking this icon once again.
Since you are using a EAP build, ReSharper may sometimes produce the so called "Internal Errors" (which are actually exceptions that have not been caught, or assertions in code that turned out to be false). If this happens, ReSharper will suggest to automatically submit the problem into the YouTrack. This will generate a Submitted request with the type Exception. Sometimes it may turn out that someone else has already submitted this error. In this case no new issue will be created, and only a comment will be added to the existing request.