Hi Team, We have a request from security team on some legal and retention questions. Could anyone please help us on below question ? We are on jira server V8.13.3 and Confluence V7.4.7versions. In both Jira and Confluence : * What is our current data retention policy? Is the data held forever? * Is there a way to "hold" (make sure nobody can edit or delete) the data if required? * How would we export the following from Jira and Confluence?* A whole project/site * Everything from a specified user(s) * Everything with a specific keyword * What file format would these exports use? Thanks!

Actually, there isn't much to the answers on these, the first one is the most important! * Data will only be deleted if one of your humans kills it. * Yes, do not give anyone the right to delete it or edit it when you want to "hold" it. You will however, need to trust your administrators to get those permissions correct, and not grant themselves delete unless you really do need something killed off or updated * To export* For a small one, site backup. Suitable for loading into another Jira or Confluence automatically * For a large one, get a copy of the attachments and a database dump * Run searches for "author = x" and export the results. However, this is not a simple question. You've got many potential definitions of "specified user" - reporter, creator, current assignee, past assignee, editors, commenters, people named in fields or the body of the content or comments. With that, you can't do a simple "extract the stuff they did", it's not going to be coherent or useful. Imagine I'd made comment 34 on an issue and said "Yay, I did that" - without the content of the rest of the issue, it's pretty useless. * Pretty much the same answer for keywords - search for them and export the whole page or issue * Depends on your choice of export method.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Legal Hold/Retention Questions about jira and confluence

jira_admin_cu

Hi Team,

We have a request from security team on some legal and retention questions. Could anyone please help us on below question ?

We are on jira server V8.13.3 and Confluence V7.4.7versions.

In both Jira and Confluence :

What is our current data retention policy? Is the data held forever?
Is there a way to "hold" (make sure nobody can edit or delete) the data if required?
How would we export the following from Jira and Confluence?
1. A whole project/site
2. Everything from a specified user(s)
3. Everything with a specific keyword
What file format would these exports use?

Thanks!

Accepted answers

Nic Brough -Adaptavist-

Actually, there isn't much to the answers on these, the first one is the most important!

Data will only be deleted if one of your humans kills it.
Yes, do not give anyone the right to delete it or edit it when you want to "hold" it. You will however, need to trust your administrators to get those permissions correct, and not grant themselves delete unless you really do need something killed off or updated
To export
1. For a small one, site backup. Suitable for loading into another Jira or Confluence automatically
2. For a large one, get a copy of the attachments and a database dump
3. Run searches for "author = x" and export the results. However, this is not a simple question. You've got many potential definitions of "specified user" - reporter, creator, current assignee, past assignee, editors, commenters, people named in fields or the body of the content or comments. With that, you can't do a simple "extract the stuff they did", it's not going to be coherent or useful. Imagine I'd made comment 34 on an issue and said "Yay, I did that" - without the content of the rest of the issue, it's pretty useless.
4. Pretty much the same answer for keywords - search for them and export the whole page or issue
Depends on your choice of export method.

All comments

Nic Brough -Adaptavist-

Actually, there isn't much to the answers on these, the first one is the most important!

Data will only be deleted if one of your humans kills it.
Yes, do not give anyone the right to delete it or edit it when you want to "hold" it. You will however, need to trust your administrators to get those permissions correct, and not grant themselves delete unless you really do need something killed off or updated
To export
1. For a small one, site backup. Suitable for loading into another Jira or Confluence automatically
2. For a large one, get a copy of the attachments and a database dump
3. Run searches for "author = x" and export the results. However, this is not a simple question. You've got many potential definitions of "specified user" - reporter, creator, current assignee, past assignee, editors, commenters, people named in fields or the body of the content or comments. With that, you can't do a simple "extract the stuff they did", it's not going to be coherent or useful. Imagine I'd made comment 34 on an issue and said "Yay, I did that" - without the content of the rest of the issue, it's pretty useless.
4. Pretty much the same answer for keywords - search for them and export the whole page or issue
Depends on your choice of export method.

jira_admin_cu

Hi Team,

I have prepared these answers, please correct me if i am wrong.

In both Jira and Confluence :

What is our current data retention policy? Is the data held forever?
1. This would be defined normally by Risk and Compliance - by default jira will not delete anything unless a user actually deletes the project
Is there a way to "hold" (make sure nobody can edit or delete) the data if required?
1. Only system administrators can delete a project. To avoid this in jira Adjust the permissions scheme to not allow any users besides jira-admins to access the project
How would we export the following from Jira and Confluence?
1. A whole project/site
  use Advanced Search and query for the project and export all the data with all fields selected to csv
  You can export a space from within the space settings (content tools --> export)
2. Everything from a specified user(s)
  1. jira - use advanced search, need to define what criteria is to be used to identify that user (is it the assignee, everything they have commented on) there are a lot of limitations to this
  2. use the advanced search in confluence but i don't think you can export that information
3. Everything with a specific keyword
  1. This will be extremely difficult but Advanced search in both cases
What file format would these exports use?
1. Most likely CSV for jira, XML for confluence

jira_admin_cu

Thanks much for quick response @Nic Brough -Adaptavist- , Could you also please check my answers below ?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server