Kudos to Atlassian for expanding the collaborative and social aspects of the Atlassian suite even further with HipChat. And congrats to the HipChat team for joining Atlassian! Chat is of course a critical aspect to collaboration along with wikis, activity streams, etc. zAgile recognized this as such a few years ago when we integrated the Jabber-based Openfire server into the zAgile Wikidsmart platform.
As always, you can count on zAgile as the Atlassian software vendor partner to contextually integrate Atlassian products. zAgile's Wikidsmart open source platform and applications deliver tight interoperability, traceability, and federated search of content (Requirements, Issues/Tasks, Tests, etc.) across the Atlassian environment, as well as with other tools (Jenkins, Selenium, etc.) and applications (Salesforce.com, etc.).
And now HipChat's chat history content will be counted among those of course. In this way, HipChat conversations may be automatically tied (via key word/topic association) to issues in JIRA, requirements in Confluence, projects in JIRA, customers in Salesforce.com, etc. No longer will chats remain isolated but can be shared (to the extent desired) and associated with all aspects of the project.
This means historical chats may be part of the contextual content served to users whenever they are doing something (like creating an issue in JIRA) or performing a search for something. For example, if they are performing a search for a specific Requirement, now they can also see the associated historical conversations along with the associated Tasks/Issues, associated Customers, etc.
The Wikidsmart platform is about teams gaining efficiency and managers gaining insight into the software engineering activities by contextually integrating content and information. Now Atlassian's HipChat's chat history will be amongst that important content to drive collaboration in an ever more contextual way.