Developer Blog

Your Friend JIRA - A Quick Guide To Bug Squashing With Boxee

Like most developers, my day begins and ends with opening my bug tracking software. It is the secretary for the coding set; the clutch organizational tool all hackers use to stay organized and keep on top of their apps.

Boxee joins many other open source projects by relying on JIRA as our bug tracking software of choice. A best-of-breed dbase for keeping track of your app’s issues and features, our JIRA implementation is available to you the Boxee developer free of charge as you release your apps on the platform.

As you get started using your JIRA account on Boxee, you may wonder how the developer community defines many of the fields in your bugs. What does “resolved” really mean? How is that different from “Closed?”

Well worry no longer with this helpful guide to using our JIRA dbase to make your app better.


  • Open: The issue is open and ready for the assignee to start work on it.
    When an issue is opened in Application project. it is automatically assigned to the Component owner.
  • In Progress: This issue is being actively worked on at the moment by the assignee.
  • Reopened: This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
  • Resolved: A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or closed.
  • Closed: The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.


  • Fixed (Default): A fix for this issue is checked into the source control and tested.
  • Won’t Fix: The problem described is an issue which will never be fixed. Or This behavior is by design.
  • Duplicate: The problem is a duplicate of an existing issue.
  • Incomplete: The problem is not completely described.
  • Cannot Reproduce: All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
May 13, 2010 at 8:05 pm