Handling eDiscovery with Atlassian Products

The organization I work for has a concern on how Atlassian products handle eDiscovery (http://en.wikipedia.org/wiki/Electronic_discovery). Is there any procedure that Atlassian has in place or can recommend to export request information regarding projects, wiki, source code, attachments information from the different Atlassian products for the Legal Department?

My first thought is it would need to be someone who is an Admin and has full access to each of the products and they would need to search for the information with the provided search functionality of each tool.

4 answers

1 accepted

0 votes
Accepted answer

Your question is rather generic, but consider implementing these kind of complex export mechanisms with the JIRA PDF View Plugin.

How? This plugin is a flexible and powerful PDF renderer for JIRA, which is also able to execute Groovy scripts while rendering PDF documents! Those Groovy scripts can access JIRA internals (JIRA projects and attachments), but also connect to the Confluence API (for wiki content), to the Stash API or to Git/SVN/etc. repositories directly (for source code). Generally speaking, you can gather information from any external resources (databases, web services, any system that provide some sort of an API). Groovy as a dynamic language supported by a plethora of libraries makes developing with it exceptionally efficient.

When all data is collected, just pass them to the PDF renderer, which will compile a PDF document merging a customizable PDF template with your data, and will download it to the client (browser).

This is perfectly doable, and you have full control over the process.

Scripting tutorial: http://midori.hu/products/jira-pdf-view-plugin/documentation/

Customization: http://midori.hu/products/jira-pdf-view-plugin/documentation/template-development

Hello guys,

Onna (http://onna.com) is the only platform that collects directly from Confluence through its API, starting from version 5.4. It supports public sites as well as private ones, hosted or behind the firewall. Hope this helps!


You will need an admin and also some sort of business process to capture the request and track. Some interesting questions to find out answers to would be what happens if you have 3 products and they are intergrated (e.g. Confluence, Jira, Stash) and you request something from one, do you have to pull related stuff from all?

So Confluence should be fairly straightforward. It allows you to export spaces, pages and attachments and uses conventional formats (PDF, CSV, XML). Jira is much less...straightforward. There isn't a good "export an issue or a project in a human readible format" that I am aware of. But for some requests I've had, screenshots of the ticket in a word doc has been sufficent. Code storage would be fairly straightforward as well, because you can always pull a specific version, etc. down to your system if you have permissions.

Following up on this, what about mass exports? Is there a back-end way to export all documents under a hierarchy without accessing each space/page individually? This would be for the purpose of providing documents to outside legal entities.

Yes, we are also in the same boat here.  Is there a way to mass export from the back end.  What we are interested in is to be able to export the given work space with out going into the individual pages.

Hi dagardc and Ben Daniel, 

If you are looking to do mass exports and providing them to outside counsel or collaborators, I would recommend checking out Onna (http://onna.com) (https://marketplace.atlassian.com/plugins/com.atlasense.plugins.atlas.confluence/server/overview). It includes an e-discovery app, which integrates with JIRA and Confluence and lets you collect and export from individual sites or entire Confluence accounts.  

Thanks for your response, Mayda.

How does Onna handles the metadata info of each page within a given work space? For example: Does it capture, who created, modified a page in a work space? 

Hi Ben,

Onna captures historical information and related metadata including:

    • Created by/on
    • Last updated by/on
    • Previous Version created by/on
    • Space ID 
    • Space Name
    • Space type
    • Ancestors for a file

Hi Ben,

I was wondering if you were interested in learning more. My direct email is mayda@onna.com 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 8 hours ago in Jira

How you can achieve compact and easy-to-maintain workflows in your JIRA( Server)

This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...

101 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you