How do your teams stay in touch and stay on top of shared projects and responsibilities in today’s remote working environment? They’re likely to use at least a few online collaboration platforms like Confluence, Jira, and Trello. No matter where your teams work, are you ready to capture these corporate communications to meet your ediscovery obligations?
We ask these questions all the time at Hanzo, and most recently we asked them on the web-based project and document management tools created by Atlassian.
We took a closer look at these specific applications in a recent webinar presented by Hanzo, “Collecting legally defensible Atlassian content and saving time too”. Here’s a quick rundown of what we discussed.
What are Atlassian tools?
Atlassian is an Australian software company that started making bug and issue tracking software for developers. They have now expanded to encompass all types of industries with three main tools:
- Confluence, an online workspace for document sharing and collaboration;
- Jira, a work management tool that allows software teams to track and resolve bugs and issues; and
- Trello, a digital Kanban board that offers a free, flexible and visual way to manage and organize projects of all types.
All these elements facilitate collaboration and interconnection. Contributors can update a task’s status or comment on documents, tickets, and Trello cards. A team managing a project with Trello can reference a document in Confluence, which itself can be linked to multiple tickets in Jira. These links are essential to the functioning of Atlassian products and the benefits they offer.
Of course, any place where business communications takes place can be a source of discovery, and Atlassian tools are no exception. This is where things can get tricky.
Ediscovery with Atlassian data is harder than it looks
I frequently get calls regarding the challenges businesses face when trying to collect data from Atlassian products or review data they have already collected. There are some commonalities between these calls, such as:
- there is no way to keep Atlassian data in place, so when the data is potentially relevant to an ongoing or anticipated litigation, companies should collect this data to ensure they are not violating their discovery obligations ;
- Many legal teams are just discovering that these data sources are relevant to Discovery Bonds, so they haven’t yet invested in a dedicated resource or process to manage them; and
- most of their collection and review efforts so far have been manual and time consuming.
One of the biggest issues with Atlassian data is how to identify relevant information. Printing 4,000 Jira tickets for the review team to review isn’t a reasonable or scalable approach, but collecting Jira data through an API also doesn’t give a realistic contextual experience. After all, Atlassian products are built on interconnects. Suppose you have a Trello project with multiple comments and a few links to tickets in an external app like Zendesk. You know that the project itself is the subject of litigation. Still, if you can’t click those links and explore the various lists and cards in Trello, let alone Zendesk tickets, it’s hard to say definitively what happened in the project.
This is one of the problems Hanzo set out to solve.
Interested in finding out more?
Check out the webinar, now available on demand, to see the demo I walked through.