Bugs and feature requests need to be filed in two different locations, depending on if the issue relates to web development tools, or Titanium-specific functionality.
The following table explains what information must be included in which fields in order for a ticket to be accepted.
Information to include
A concise summary that makes it easy to determine the nature of the issue
One of the following descriptions may be chosen to describe the issue's impact on your project :
Find a component which most closely describes the problem area
Studio version: copied and pasted from Help / About
a concise, factual, description
Always attach the Studio log, and depending on the issue, various other logs are helpful. See Accessing the Log File for which logs to attach. You may also be asked to attach your configuration log. See Determining Your Studio Configuration.
Web tools feature requests/bugs
Please file a report at http://jira.appcelerator.org/browse/APSTUD. Follow the checklist above and the steps below when creating a bug report.
Titanium tools feature requests/bugs
Please file a report at http://jira.appcelerator.org/browse/AC. Follow the checklist above and the steps below when creating a bug report.
Requesting a feature
- Search Jira in the relevant project thoroughly for similar issues. If it already exists, add yourself as a watcher. The more watchers a feature has, the higher likelihood it will be implemented.
- Make sure that the request is something that actually requires a change in the core product. For the SDK, it may be best implemented as a module. For Studio, it could be implemented as an Eclipse plugin.
- Describe as clearly as possible the feature and how you intend on using it. For features that are part of the SDK, include sample code demonstrating how'd you like to interact with the APIs. Pseduo-code is fine.
- Explain why the feature is important, especially if the usage is non-obvious. The more people that are interested in the feature, and the more people it will benefit, the higher priority the feature will get.
- Add test cases to let us know that we implemented the feature correctly.
- If there are Q & A posts around the feature, add those as well.
- If you can, write the feature yourself and submit it to the project. This speeds up the process considerably!
Bug submission steps
- Find possible bug
- Search Jira in the relevant project thoroughly for similar issues
- Once certain of a bug:
- Create a Jira ticket (one ticket per bug)
- Keep it as concise and as factual as possible
- Include your usecase, and all the information described in checklist below
- Watch ticket, to show your support for the ticket's resolution
- If coming here to create a ticket from another forum, help others by posting the ticket's URL back in the source location.
Creating a good use-case
A "usecase" is a working script that reliably reproduces a specific bug. The best usecase is one that contains the least possible code while still demonstrating the bug.
- Try the issue in a new workspace or a new project to see if that make a difference
- Include exact steps to perform the actions in your workspace. In particular, when referencing editor errors, a sample document with cursor positions, and expected and actual output is invaluable
- Try and create the smallest possible sample that illustrates the problem
Creating a Jira ticket
- Open the Jira project page above. Tickets may be created in APSTUD directly, but TISTUD tickets will need to be verified by support personnel first. Please do not add Titanium tickets in the Aptana Studio tracker--they will be marked as invalid and you will be asked to resubmit the issue.
- Select from the list of ticket types in the top right-hand corner, although usually only Bug, Improvement or New Feature will be appropriate
- Complete as many fields as you can. Refer to checklist for help with this
- As the reporter, you will automatically receive any updates to the ticket. However, it's always a good idea to also watch the ticket if its resolution is crucial to your projects, in order for our team to gauge the issue's impact on the community from the watchers list
Thank you for your time!