Integration and Interoperability between Salesforce, Confluence and JIRA has never been more powerful than that offered by zAgile's open source Wikidsmart CRM, which includes the connectors for Salesforce, Confluence and JIRA.

Wikidsmart CRM allows for bidirectional integration of information in Salesforce with internal enterprise tools and applications. Specifically, Wikidsmart's Salesforce connector provides integration and interoperability with Atlassian's Confluence wiki and JIRA issue tracking application. Through this integration, Sales and Account Management teams can collaborate on, track, and manage various account-related tasks.

Similarly, customer support teams can track the status of various customer cases, as they are processed through internal delivery cycles.

Furthermore, this integration is flexible and extensible, as it can extend to any Salesforce objects, including custom objects, that need to be brought into the enterprise.

It is also possible to integrate this information with other tools and applications, via packaged or custom-built Wikidsmart connectors for those applications. The key to this integration, as discussed below, is Wikidsmart's Context Server (WCS) which extracts information from Salesforce and relates it with concepts from other tools, exposing this cohesive information network to all applications.

While Wikidsmart CRM has broad applicability with respect to integration of Salesforce with enterprise applications, here are some of the more common examples:

  • Case management
    Customers Support can create and track JIRA tasks from within Salesforce. Each task automatically maintains the context of the customer case from where it is initiated. As the task moves through the resolution workflow in JIRA, its realtime status is reflected back within the context of the Case(s) it represents in Salesforce and can also be reflected with the Account that is associated with the Case. Conversely, any task in JIRA may also be linked to one or more cases via a custom field. In this case, each linked case will automatically reflect the task details within Salesforce. And finally, Customer Support can also interact with JIRA tasks, add attachments and comments, change priorities, etc. from within the Case application in Salesforce.
  • Customer on-boarding
    Customer on-boarding typically involves a series of pre-defined activities and tasks related to, for example, training, enrollment, implementation, and customer support orientation. Furthermore, these activities cover a number of different groups within the organization. Wikidsmart provides a number of capabilities that facilitate improved participation and collaboration between all teams that are involved in customer on-boarding activities. It allows for the initiation of various tasks and workflows related to the customer, for easy tracking and reporting across all of these activities, and provides an extensible customer-focused dashboard for a unified and consistent view.
  • Customer Account Management
    Similar to the activities and tasks associated with customer on-boarding, ongoing customer account management also entails tracking various activities and deliverables involving a customer and/or an account. These could be ad hoc tasks, such as SLA review, quarterly roadmap update, and exploring upsell opportunities. It could also involve tracking features and bugs through product delivery cycles which are pertinent to the customer. And finally, it could involve specific services-related engagements with the customer. Wikidsmart's integration of Salesforce with internal applications, especially those related to services and product delivery, allows teams to participate and collaborate on these activities and gain consistent visibility into them to ensure prompt escalations towards achieving high customer satisfaction.

Download open source Wikidsmart and check out the powerful features for yourself.

A re-post from my blog on typepad

I am pleased to announce that all the power of zAgile's Wikidsmart's infrastructure and applications are now open source. Now all software engineering delivery teams and executives can easily and affordably overcome the problem of disparate teams and tools easily.

Whenever you integrate content, whether it's point-to-point or else with a service bus or traditional data federation layer, you get the same problem. The content is really only mapping data to data with no intrinsic understanding of the process or context of how the data is related. It's essentially dumb mapping. And it's a tedious, expensive effort that is difficult to measure in terms of ROI. So people simply don't do it. And that's why we still have the mess and an additional reason for software delivery deadlines being missed.

The Wikidsmart platform and applications offer the solution. Wikidsmart's core is a context server based on semantic web technologies. I determined that the integrated ALM solution had to have a number of characteristics. First, it had to follow open standards to be approachable to a wider audience. It had to recognize process, metadata, and context all in one. As I did my research, I realized that the WC3 standards body, led by Sir Tim Berners-Lee, was trying to solve a similar problem for the web. They led the definitions for semantic web technologies in order to interconnect content of the world's websites. I realized that some of those same technologies are the ideal vehicle for integration of content across the enterprise. Finally, we determined that our solution should be open source. Semantic web technologies are not yet widely known, and the open source nature tends to encourage people to experiment, learn, and contribute to extending the solution - and eventually adopt those solutions in a much more widespread way than closed systems would have otherwise. I think Big Data technologies like Hadoop and the NoSQL movement have demonstrated that well. So what we have ended up with at the core of the Wikidsmart platform is the Wikidsmart Context Server, which is an ontology-driven semantic framework that integrates content bi-directionally as a sort of semantic bus.  It serves contextually relevant content from across the enterprise with the application or tool being used by the team member, or contextually composite information for example for an executive dashboard.

Of course, we are speaking of a paradigm shift in the way we think of content, metadata, processes. We went from mainframe to client/server to the internet. Those were all major changes that were inspired by big pains. I think we all agree that the pain is there in content integration. People are still trying to solve the problem with old approaches. People are still thinking SQL and point-to-point application integration primarily. We believe that open sourcing Wikidsmart will hasten its adoption and make the problem of lack of ALM integration a story of the past. I invite you to download <>  today for yourself and check it out.

zAgile Teamwork now integrates Selenium to its platform alongside Confluence and JIRA. This level of integration now allows you to:

  1. manage Test Cases in Confluence,
  2. integrate them with Features and Requirements,
  3. associate Selenium scripts to each Test Case, and
  4. use JIRA Workflow to run the scripts and capture the results

You can view Test Case execution history, and trace Test Case results to Requirements and Releases.
To scale the testing efforts, you can execute the scripts in the cloud.

To check out examples of this integration – visit Sauce On Demand Test Suite

zAgile Teamwork 3 Professional is now available and has a number of significant enhancements and capabilities:


  • Improved Usability of Template-driven Pages
  • Improved Integration with JIRA
    • Create background JIRA Tasks from Confluence
    • Manage JIRA Workflow Tasks from Confluence
  • Integration of Software Projects with CRM Concepts (Customer Account, Customer Case)
  • Table-based Drop-down Action Lists in Confluence for improved Usability
  • Redesigned JIRA Plugin for faster installation, customization, and improved compatibility
  • Improved integration between Features, Use Cases, Requirements and Tasks
  • Table-driven Task Execution from Confluence
  • Support for JIRA User and Group Directories


  • Confluence 3.5
  • JIRA 4.3

Integrations (via separately available zAgile connectors)

  • Portal
    • JBOSS/Gatein Portal
  • CRM
    • Salesforce between JIRA and Confluence
  • Version Control
    • Perforce
    • Subversion
  • Continuous Builds
    • CruiseControl
    • Hudson

zAgile Teamwork 2.0 Professional is now available and has a number of significant enhancements and capabilities:


  • Requirements Management with Confluence & JIRA
    • Define requirements and related artifacts in Confluence via easy-to-use templates
    • Associated these requirements with Projects, Components and Releases in JIRA via these templates
    • Create requirement review/approval tasks in JIRA from within Confluence, automatically initiate requirement approval workflow with notifications
    • Create development tasks for each requirement from within Confluence, automatically linked back to the originating requirement.
    • Task statuses are automatically reflected back in Confluence on the requirements pages
  • Test Case Management with Confluence & JIRA
    • Define test suites, test cases, test specification documents in Confluence via easy-to-use templates
    • Associated these with Projects, Components and Releases in JIRA via these templates
    • Create test execution tasks in JIRA from within Confluence, automatically initiate test execution workflow with notifications
    • Track test execution results in Confluence per iteration, component, requirement, release and project.
    • Task execution statuses are automatically reflected back in Confluence on the test definition pages
  • Reports
    • Pixel-perfect reports based on JasperReports engine for building project and release dashboards
    • Design custom reports via zAgile's iReport plugin
    • Render reports in Confluence in any page with drill-down and traceability
  • zAgile's Smart Search as OpenSocial gadget representing integrated information from both Confluence and JIRA in any OpenSocial container
  • Significant performance improvements to improve query response time within Confluence
  • Machine-based semantic annotation of wiki content to provide context of key terms on any page


  • Confluence 2.8 - 3.3.
  • JIRA 3.1 - 4.1
  • Interoperability in JIRA Studio.
  • Interoperability with other applications

Integrations (via separately available zAgile connectors)

  • CRM
    • Salesforce between JIRA and Confluence
  • Version Control
    • Perforce
    • Subversion
  • Continuous Builds
    • CruiseControl
  • Hudson

zAgile Teamwork 2.0 Professional is slated for release June 2010 and will have the following capabilities:

  1. Compatibility
    1. Support for Confluence 3.2.
    2. Support for JIRA 4.1.
    3. Interoperability in JIRA Studio.
    4. Interoperability with other applications
  2. Features
    1. zAgile's Smart Search and other OpenSocial gadget representing integrated dashboards (for both Confluence and JIRA).
    2. Easy creation of JIRA issues from within Confluence with automatic 2-way links between the issue and its source artifact in Confluence.
    3. Significant performance improvements to improve query response time within Confluence.
    4. Machine-based semantic annotation of wiki content
    5. Templates for representing software engineering methodologies, such as Agile, Open Unified Process, etc.
    6. Integrated Workflows for Agile Software Development across all tools.
  3. Integrations with:
    1. CRM
      1. Salesforce between JIRA and Confluence
    2. Version Control
      1. Perforce
      2. Subversion
    3. Continuous Builds
      1. CruiseControl
      2. Hudson

zAgile Teamwork 1.3.2 has now been released and may be downloaded from the link below.

The key features of zTeamwork 1.3.x are:

  1. Support for Confluence 3.0 and 3.1
  2. Support for JIRA 4.0
  3. zAgile's Smart Search as OpenSocial gadget (for both Confluence and JIRA). Smart Search allows you to execute faceted search for Software Engineering concepts (Projects, Issues, Tasks, Requirements, Test Cases, etc.) from either Confluence or JIRA, independent of where the actual data resides.
  4. Two-click creation of JIRA issues from within Confluence with automatic 2-way links between the issue and its source artifact in Confluence.
  5. Significant performance improvements to improve query response time within Confluence.

Download zAgile Teamwork 1.3.2GA here

zAgile Teamwork is a wiki application for software engineering collaboration, and it is built upon zAgile Wikidsmart, the open source semantic wiki engine. zAgile Teamwork is an elegant solution to the age-old problem of disparate engineering teams, tools, and processes, and knowledge. Teamwork leverages the Atlassian Confluence enterprise wiki and the Atlassian JIRA issue tracker to deliver simple, yet powerful collaboration for software engineering, in a completely integrated and extensible environment. Teamwork supports Requirements and Test Case management via Confluence smart templates, and it seamlessly integrated with JIRA Projects, Tasks and Bugs. As everyone's engineering environment is different, Teamwork also integrates with other tools that fit your needs, including those covering: Version Control, Continuous Build, Requirements Management, Issue Tracking, Test Case Management, Project Management, etc.


[zAgile Teamwork] includes the following features.

  1. Wikidsmart features:
    1. Capture content, in a consistent fashion, with forms. zAgile's infrastructure "recognizes" the content captured in these forms, and it organizes the content with respect to other semantically meaningful information for easy future retrieval and reference.
    2. Find precise information quickly and easily by searching with respect to semantically meaningful topics. Therefore, you can find information in a contextual way within your wiki (e.g., zAgile can recognize "glasses" as "reading glasses" rather than "drinking glasses")
    3. Automatically generate new pages based upon content captured in forms or from external applications that have zAgile Connectors
    4. Augment the software engineering knowledge model by importing "ontologies," knowledge models for specific domains that you may already have, build yourself, or have the zAgile services team build for you. For example, you could import a knowledge model for healthcare, financial, or other domains.
  2. Software engineering knowledge model ("ontology")
  3. Wiki "smart templates": wiki forms for software engineering (e.g., Requirements, Test Cases, Projects, etc.)
  4. JIRA Connector for deep bi-directional integration of information between Confluence and JIRA. For example, JIRA information can be easily exposed in Confluence with an embedded query, and likewise a customizable tab page called Properties in JIRA displays content from the wiki that takes into account the context of the current Project, Issue, or Task of interest.