Community Issue/Bug Tracking

Digital Network Architecture. Abstract technology. New York

We are very interested in identifying, prioritizing, and resolving bugs raised by members of the community. Without your help, the Titanium Platform cannot hope to reach its full potential. Many of you have been helping us in this ongoing effort by logging tickets in Q&A that are:

  • well-researched (accurate, no duplicates)
  • clear
  • concise
  • factual (no conjecture)
  • well-defined (including platforms used, SDK versions, environment)
  • include a minimalist usecase

These tickets have been very much responsible for making Titanium a better platform, far more quickly than it otherwise would have been.

To improve this process, we have created the Titanium Community project to act as a clearing house for new tickets. A ticket created here will be checked for completeness and improved by a member of our team or a qualified Titan, with the help of the person who raised it. Using this process reduces the time our core teams will spend administering tickets, when they could be writing code.

We will then submit the ticket to the respective core project, where our internal teams will set its priority, and develop and test a solution. As a reporter, you will automatically be notified of any updates, and we encourage others to watch tickets that are hindering their projects, to help us understand an issue’s prevalence. Although we must emphasize that we cannot, regrettably, guarantee any response times, we do have regular “bug scrubs” where we pay close attention to our community and customer feedback.

To get started contributing to this project, please register for an account on our system. Be sure to keep in mind the guidelines above, together with those explained in the Submitting Bug Reports guide.

Thanks in advance for all of your keen eyes! 😉


  1. Tony,

    Thanks for publishing this notice. The Titanium Community project is a great concept for those of us who feel that we have discovered true bugs and have taken the time to reduce the malfunctioning code down to a usecase.

    I would also like to see some kind of rating system or “points” system that would prioritize bugs reported by significant contributors. In other words, if I take the time to track down a bug and send you the minimal usecase that duplicates it and explain it well, and I do this with say, 5 to 10 bugs, I have spent a significant amount of time which will save your developers a significant amount of time and will improve your product in the eyes of its users. It would be nice if that time I spent was rewarded by having my bugs prioritized higher and fixed sooner.

    Also, it would be great if your community support engineers could harvest potential bugs from the Q&A activity, check them out on their own, and respond to the relavent Q&A entries. I frequently see trends in the Q&A that are clearly bugs (with multiple postings about the same problem), but no Appcelerator response is given.

    Thanks, -Shawn

  2. Shawn,

    I totally agree with you.

    I also reported number of bugs, give suggestions how to improve Titanium and I’m activity participating in Q/A. What bothers me is that some issues related to some basic functionality are not fixed and are not prioritized (for example: remove method of scroll view doesn’t work, window close event is not fired if window closes from some event handler – button “click” event handler for example, which is pretty common use-case, etc.).

    It would be great if my effort would be awarded by prioritizing some of the issues that I think that are important. I understand that customers that are paying for support are the most important to Appcelerator crew, but helpful community members should be important also.

  3. Ivan & Shawn –

    We agree. This is a start to a community-led initiative. Note that ‘watching’ a bug is equivalent to voting up an issue. The more people that watch an issue, the higher the priority we place on it.


  4. I think this is wonderful, but unfortunately my experience of using JIRA (the ticketing system) is that even though I have been concise, written up use cases, and documented everything in detail, I often get ZERO response from Appcelerator on REAL issues I can replicate and have reported to you.

    As an example, here are two tickets created around 1.5 weeks ago, which have not even been acknowledged as received:

    I love the direction, and I hope you do as you say, but as it stands unfortunately I see a lot of talk, and very little action. I hope you prove that I am wrong.