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

Hug JIRA with Boxee On Monday

Next Monday, the May installment of what is becoming a favorite Boxee tradition - JIRA Hug Day! “JIRA Hug Day” is our internal name for taking one day when everyone in the company - even non-technical folks - jump into our bug tracking software and squash as many bugs as possible. The result of previous Hug Days can be found evident in the notes of our last release, increasing the overall stability of the experience and enriching our user experience.

This time around, our engineers would like to invite you the Boxee application developer to participate for our marathon squash fest. Your apps are the crown jewels of the Boxee experience and we’d like to take a day to polish them with you.

Here’s how you can participate:

1) Get on JIRA

You can sign up for a JIRA account here. This will allow you to create your own filters for your apps, comment on bugs, and watch the issues that are important to you.

2) Make Sure Your App Is A JIRA Component

A JIRA component is created for the boxee-apps project for every app in our main app repo, however JIRA is great for tracking the bugs of apps distributed in third party repositories too. Your app does not need to be in the App Library to be on JIRA. If you don’t see your app listed, be sure to email me at rob [at] boxee [dot] tv to get a new one.

3) Grab Some Bugs!

Use this guide to find the bugs that are important to your apps and get to squashing!

My goal for the development community this Monday is to turn the summary for the boxee-apps project upside down, meaning we resolve more bugs than we took in for the month of April.

Hop on JIRA, get plugged in on the forums and on #boxee on, and show JIRA, and your users, some springtime love.

April 27, 2010 at 4:26 pm