Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. review the documentation
  2. search JIRA for similar known issues
  3. search the Q&A for discussions about the issue between our community members
  4. create a test case (it's a prerequisite for posting to the Q&A and JIRA). Follow the guidance in Creating a Test Case
  5. post a question in the Q&A to garner the community's opinion about the issue and collaborate on a workaround. Include your test case with the rest of the information.
  6. create a JIRA ticket, only after there is no doubt about the bug's existence, Create one ticket per bug, bearing the following in mind:
    • keep to the point: concise, complete and factual tickets are the most appreciated
    • include all the information: without a test case and all the information described in the JIRA Ticket Checklist, we cannot accept your ticket
    • watch your ticket: This makes us aware of your vote for the ticket's quick resolution
      NOTE: Your JIRA login is different than your AMPLIFY Appcelerator Services login.  If you do not have a JIRA login with us, please select the link under the login boxes to contact the JIRA administrators and request a login. Logins typically provided within one business day. 
  7. post the ticket's URL to your Q&A question. Add this as a comment under the question that helped you most and mark it as "best" to make it easy for everyone to find


Assuming you have consulted the community via the Q&A, and you have your test case to hand, you are ready to create a ticket:

  • open the JIRA Titanium Community project page. See the #Projects Overview section for more information about the projects.
    NOTE: Your JIRA login is different than your AMPLIFY Appcelerator Services login.  If you do not have a JIRA login with us, please select the link under the login boxes to contact the JIRA administrators and request a login. Logins typically provided within one business day.
  • select from the list of ticket types in the top right-hand corner, although usually only Bug, Improvement or New Feature will be applicable
  • complete as many fields as you can. Use the JIRA Ticket Template as a starting point, and refer to the #JIRA Ticket Checklist below for the information that is required
  • as the reporter, you will automatically receive any updates to the ticket. However, it's always a good idea to also watch all tickets where the resolution is crucial to your projects. This helps our team gauge the issue's impact on the community, from the total number watchers in the list





Information to include


A concise summary that distinguishes it from other tickets, making it easy for the core team to determine at a glance the nature of the issue.
Format: <COMPONENT>: <SUB-COMPONENT> - Description (eg. "iOS: Facebook - Unable to login on iPod")


Leave as default


Leave as default


Optionally, one of the following descriptions may be chosen to reflect the issue's impact on your project: 

  • Blocker: issue is blocking project
  • Major: crashing or incorrect behavior issue that may have a workaround or is not stopping ship
  • Minor: crash or incorrect behavior that does have a reasonable workaround or low impact
  • Trivial: functions correctly, but appearance/functionality needs improvement
  • None: default


Choose a component from the list


The tested environment (only include the versions of each component that exhibit the problem and have been physically tested)

  • Titanium SDK version: number, build date and build hash, or output to the console output at application launch 
  • Javascript Engine: Rhino / V8  V8 
  • Platform & version: iOS x.x, Android x.x, OS X x.x, Windows x, and/or Ubuntu x.x 
  • Device Details: iOS simulator, Android emulator, or physical device model 
  • Host Operating System: OS X x.x, Windows x, or Ubuntu x.x 
  • Titanium Studio version: available in Help > About



A concise, factual, description containing the following sections (use the JIRA Ticket Template as a starting point): 

Explanation of the problem, including the actual behavior and the expected behavior 

Test case 
Steps to reproduce plus simple working code that demonstrates the issue and follows the Creating a Test Case guidelines, placed within a {code} markup block in the body of the ticket 

Community Discussion 
A link to the Q&A question in which you asked the community to verify the observed behavior 

Logged messages from the following locations, depending on the problem, placed within a {code} markup block in the body of the ticket: 

  • Android and iOS Development: Titanium Studio console output of exceptions
  • Packaging: contents of build.log (Android: <PROJECT>/build.log, iOS: build/iphone/build/build.log)
  • Titanium Studio: contents of menu item Help > Titanium Studio > View Log File (contents of <workspace-dir>/log file) 


Attach images and assets, but try to keep code in the description field 


The only valid labels are regression for regressions and parity for differences between platforms. All others will be removed before the ticket is accepted.

We do not underestimate the time and conscientiousness involved in raising good tickets, and we very much appreciate it. Thank you for all your efforts!