We are pleased to be running this month's Plugin of the Month webinar with Orasi. Orasi s an Atlanta-based software reseller and professional services company focused on enterprise software quality testing and management.
This Wednesday, David Brown of Orasi will present on the JIRA Bridge for HP Quality Center. This is an enterprise-class integration solution that enables organizations to harness the full potential of JIRA and HP Quality Center software because it synchronizes defect information between the two tools. This bridge enables your QA and development teams to collaborate efficiently by coordinating all issue information between the teams.
UPDATE: WEBINAR POSTED HERE
Just a quick reminder for the first Voice of the Customer (VOTC) webinar of 2010 with Zend Framework.
Zend Framework is arguably the most popular PHP framework available, boasting millions of downloads and an active community. Early in its history, a decision was made to use JIRA and Confluence as developer tools to help manage issues, feature requests, and our proposal workflow. The tools have weathered a number of upgrades, a rapidly expanding user base (and thus issue reports), a growing number of contributors, and provide immense benefit for the Zend Framework community.
Update: webinar posted here
Please join us for the first Voice of the Customer (VOTC) webinar of 2010 with Zend Framework.
Zend Framework is arguably the most popular PHP framework available, boasting millions of downloads and an active community. Early in its history, a decision was made to use JIRA and Confluence as developer tools to help manage issues, feature requests, and our proposal workflow. The tools have weathered a number of upgrades, a rapidly expanding user base (and thus issue reports), a growing number of contributors, and provide immense benefit for the Zend Framework community.
Update: webinar posted here
Tomorrow is our Plugin of the Month webinar with the JIRA Connector for Jama Contour.
The JIRA Connector integrates Jama Contour, a popular tool used for managing requirements, with JIRA. This integration connects business teams responsible for product requirements and planning with development teams responsible for implementation. If you're unfamiliar with Contour, it's a Web application used by analysts and product managers to gather and manage requirements, track changes to scope, and plan releases.
The JIRA Connector is a plugin for Contour that keeps the two systems in sync and automates the communication between departments - saving time, eliminating costly errors and allowing people to work in their favorite tool.
Update: VIDEO HERE
This morning we had a little bit of a snafu. A customer, with the best of intentions, added the entire JIRA User Group to the Cc Group field - a custom field created for our JIRA instance - of their support issue on support.atlassian.com. They didn't realize that this group has more than 30,000 members. When they hit save they triggered a tsunami of email notifications that landed in the inboxes of thousands of other unsuspecting customers. Man, were we embarrassed.
We sent an apology out to the customers who received those emails - many among you - explaining what happened and assuring folks that we fixed the issue by removing the "Cc Group" field on support.atlassian.com. But we also wanted to explain a bit about how that field is used, why it wasn't disabled before, and other ways to achieve the same outcome now that this field is disabled.
What is the Cc Group field?
The "Cc Group" is a custom field that was created for our JIRA support instance, and used internally by Atlassian and by a select group of customers to update a group of JIRA users about a specific ticket. Once Cc'd on a ticket, the group will receive notifications regarding any status changes and/or updates. However, enabling this provided access to global groups such as jira-user, which contains all JIRA users. We hadn't removed it before because it was being used by customers, and because we simply didn't consider a customer adding all users of the system to the Cc field.
Hey, I was using that. What can I do now?
We have now removed the "Cc Group" field, so this can no longer happen. But there is a workaround. If you were using the "Cc Group" field, you can achieve the same result by creating an internal email alias containing each of the users previously in your JIRA group on support.atlassian.com. Instead of using the "Cc Group" field you can use the "Cc User" field with the new alias.
Again, we're sorry for the extra email so many of you received, and we've definitely fixed it. Back to your previously scheduled program.
Copyright © 2009 Atlassian Pty Ltd.
