David Cook

Atlassian recently hosted a webinar entitled "Greenhopper for JIRA: Not Just for Agile Developers." The webinar featured demos from Jean Christophe Huet, the father of GreenHopper, and Cody Burleson, founder and President of Burleson Technology Group. In addition, the webinar included over 45 minutes of questions!
Cody Burleson.pngJC Huet.png
JC showed how GreenHopper can be used by pretty much any JIRA user and informed the audience that GreenHopper's two main goals are to provide a simple and interactive interface and increase visibility and traceability of JIRA projects. He demonstrated how GreenHopper can help you: update issues quickly, prioritize issues, manage subtasks, manage versions, schedule issues, and update statuses quickly.

Then Cody Burleson took the stage and expanded on his GreenHopper blog series by describing what he does and how he uses GreenHopper and JIRA. He is new to GreenHopper (his 30-day trial expired two days before the webinar), but he already finds the plugin extremely helpful. Referring to GreenHopper, Cody commented: "only once in a while does a product come around that really delights you, and when I find something like that it's exciting!"

After Cody finished his demo, JC and Cody spent the next 45 minutes answering questions from people watching the webinar. Topics included the burndown chart, custom fields, custom issue types, test integration, etc. Unfortunately, a technical difficulty cut off about 20 minutes of the Q&A, so the recorded version of the webinar is missing the last few questions.

Hopefully the webinar will help you learn more about GreenHopper and JIRA!
Check out the webinar:


So far, several attendees have downloaded or bought GreenHopper. Join them!

4 Comment(s)

Hi , Do you have any suggestions on how we can collate multiple buckets containing different types of issues that might be included in a sprint such as bugs, development task, customer tickets etc. We currently have a large number of issues in different silo's and would like to get them into one backlog but also available in their own issue category. Does greenhopper have any concept of an Uber Version that can span categories. We have been examining it and i cannot see anything like this.

By Eain at June 23, 2009 12:39 AM

Feedback on the webinar recording:
Unfortunately the video quality is really bad. You can't read anything. If you have already worked with Greenhopper you get an idea what is going on, otherwise not.
I toggled the quality to "HD on" but this has no effect.

Michael

By Michael at June 24, 2009 6:27 PM

You can have different types of issues (bugs, development tasks, customer tickets, etc.) in one backlog as long as you use the product or project version to represent your backlog.

What we do is use Manage Versions view on Administer project to create Sprints. So, you could have, for example RELEASE 1 (that would be a version). Then you could have SPRINT 1, SPRINT 2, SPRINT 3. In GreenHopper, you just make RELEASE 1 the Master to SPRINT 1, SPRINT 2, SPRINT 3. You can call any issue with an unassigned version the backlog and just assign those issues to the Fix Version when you want them to be part of a particular sprint. Alternatively, if you do not ever want Fix Version to be unassigned, just create a release called "Backlog" or "Release 1 Backlog".

In other words, any issue not assigned a Fix Version is your backlog. Or any issue assigned to a version called "Backlog" is your backlog. By creating versions for for named backlogs, you could have several backlogs. And this might also help you query issues. Your choice.

By Cody Burleson at July 15, 2009 4:55 AM

Would love to see an updated tutorial based on JIRA 4! Also agree with Michael on the recording quality.

By Adam Wride at November 25, 2009 8:12 AM

Post a comment





Remember personal info?

Type the characters you see in the picture above.