Getting Silky With the Go2Group JaS Plugin

Does your firm utilize Borland's SilkCentral Test Manager for its test management needs, while your development team is locked into Atlassian's JIRA issue tracking system for development efforts, and you are trying to find a way for the two teams to collaborate in a more cost effective manner? Why not give the Go2Group JaS Plugin a (free) trial?

The Go2Group JaS Plugin allows developers in JIRA to display a list of available SilkCentral test cases in a JIRA window. No need to purchase additional user licenses. No need to force either team to learn a new tool. No need for expensive consulting services to configure one system to capture the same features found in the other.

The result is a cost-effective, transparent, and seamless collaboration solution, built around the products and knowledge already contained in-house.

To review more information on the Go2Group JaS Plugin, click here. For specific questions, contact us today!

---
Go2Group, Inc.
www.go2group.com

Go2Group CRM Plugin - Collabarate. Now.

We gave a discusson on support and sales teams being integrated with other internal teams within an organization. The basis of this discussion was the Go2Group CRM Plugin, and our experience in working with development and sales teams.

We put the following presentation together for our discussion, and thought it'd be a good idea to post it here as well.

Go2Group CRM Plugin

View SlideShare presentation or Upload your own. (tags: go2group jira)

Have questions, or looking to evaluation the latest Go2Group CRM Plugin? Contact us today!


---
Go2Group, Inc.
www.go2group.com

Confluence - A Complex & Timely Move Made Easy

Recently, Go2Group was asked to provide some assistance with Confluence, Atlassian's enterprise wiki product. We use Confluence internally for collaboration across different teams in different locations, as well as for our support site to provide product information to our customers.

Needless to say, we are experienced Confluence users and administrators, which makes a client's support request that much more imperative - we're not sure what we'd do if the wiki was down!

This particular client was preparing for a big moving day - from a new server, a new database server, a new version of their databse, and a new version of Confluence. All at the same time. This engagement certainly had the opportunity for many points of failure, but it turned out to be one of our smoothless deployments.

In preparing for this engagement and while providing the required services, we leared a few things:

• When upgrading to a new version of Confluence, take inventory of the currently installed plugins. Some plugins can be updated directly from Confluence's plugin repository, but many will have to be updated manually by uploading the new JAR files.
• Confluence is a very stable product, and one that is very tolerant when moving to a new plaform and/or database.
• The smoothness of this transition was partially due to the way Confluence was configured in this environment - the client was very careful not to install plugins just because they could. This client was very particular about which plugins were to be installed based on their need and frequency of use.

Confluence is a great product for a number of reasons, one of which is it's ablity to be easily customized and extended. However, there is a great temptation to customize it to the point it is no longer recognizable as a wiki while installing different plugins because they are easily available.

We would certainly agree that these options are nice, and sometimes required. At the same time, we'd like to preach the gospel according to prudence: Everything in moderation.


---
Go2Group, Inc.
http://www.go2group.com/