Last week, I was a guest on a special Zendesk integration webinar talking about integrating your Zendesk with Atlassian JIRA.
What did you miss?
After a brief introduction to the session, we covered a demo of JIRA 4 (@7:15), a walk-thru of the configuration details for both Zendesk and JIRA (@18:25), and a demo of the integration in action (28:00). This was followed by Q&A from the attendees (@44:00).
The webinar recording is now up on AtlassianTV, and I have included a copy here:
You may recall a recent post in which one of our developers talked about his plugin for JIRA that provided a cleaner UI when accessed via iPhone.
Making JIRA More Mobile
Andreas is at it again, this time tackling the problem of viewing JIRA 4.0 gadgets while on-the-go. He's written a JSP page that will allow visitors to visit each gadget on a dashboard page individually, which greatly improves performance on mobile devices.
"With the JSP page, users can bookmark a URL on their phones such as http://localhost:2990/jira/gadgets.jsp?d=10000 (where 10000 is the dashboard id) which will then provide them with a list of all the gadgets on that dashboard."
VersionOne recently published and distributed their State of Agile Development survey. Lots of very interesting data points worth reviewing. The most notable being the specific tools currently used by respondents of the survey:
JIRA was the leading development-specific tool -- used by 24% of respondents! Only the generic project management tools from Microsoft (Excel and Project) were more widely used.
I wonder..
Given that over 17% of JIRA customers use GreenHopper for agile project management, and I imagine even more use it within agile development teams. Therefore, I'm a bit surprised GreenHopper was not on the list. I wonder if it was even an option in this survey... maybe we'll find out next year.
The latest release of Pivotal Tracker includes support for a number of issue trackers, including our very own JIRA.
Setting integration up is easy enough (instructions here), just make sure to allow remote API calls in your JIRA general configuration settings. It's a one way integration, meaning you can manipulate issues from JIRA in Pivotal, but not the other way around.
How JIRA Works With Pivotal
As soon as you move a JIRA issue from your 'JIRA' column to any other in Pivotal, a comment is added to the JIRA issue explaining what action was taken.
Finishing an issue will change it's status to 'Closed' in JIRA. Only the default JIRA workflow is supported at this time, so if you're using a custom workflow, the change in Pivotal won't be reflected in the status of the JIRA issue.
Check out the screenshots below, and leave a comment if you've checked it out for yourself!
Next week, I'll be a guest on a webinar hosted by Zendesk, talking about the advantages of integrating JIRA with your Zendesk. In the session, we will cover the following:
How JIRA is useful for bug tracking and project management
What data gets passed between applications
What a development project without bug tracking tools looks like
How sharing information between departments can increase productivity
Zendesk extends good help desk karma to any company looking to offer professional-grade support service with very little effort. Using the benefits of Web-based communications and social media, it has helped companies of all sizes move their help desk and customer support operations to the Web. Companies such as Twitter, MSNBC, Scribd, IDEO, John Lewis, and Books-a-Million can attest to the fact that with Zendesk, the name of the game is simplification.