Content
View differences
Updated by Judith Roth 8 months ago
After talking with Wieland again and doing some research, I try to summarize this anew. in the comments of <mention class="mention" data-id="67403" data-type="work_package" data-text="#67403">#67403</mention> <mention class="mention" data-id="42086" data-type="user" data-text="@Wieland Lindenthal">@Wieland Lindenthal</mention> wrote:
First: We need > For work package **Activity** tab we started to distinguish between attachments that were uploaded in go the Editor ("inline attachments") and attachments that were uploaded following route (and we still haven't adopted to this in the "Files" tab.
### Current state
In the **classic documents** module, there is no difference between work package description): The life cycle of inline attachments and attachments uploaded in is managed through the "Files" tab. All of rich text field. If you delete them are shown in the "Files" tab.
In **work packages**, inline attachments (uploaded with CKEditor), e.g. images, rich text field then they are shown also deleted as attachments. They do not get listed (anymore) in the "Files" tab as well. If such a file is removed from the work package text, it is not removed from the "Files" **Files** tab.
However, files that have been added to a **comment to a work package**, are The reason for not shown in the "Files" tab. If a comment with a listing them like other attachments: often people place screenshots and other indistinguishable file (e.g. image) is created and the names into rich text is edited and the file link removed, we also remove the file from the database and storage. update them there. This is important for GDPR compliance, since the user would otherwise have no way leads to delete the file.
Wieland argued, that it would be nice for users to distinguish between inline attachments a long and attachments uploaded unmanageable list of files in the "Files" tab, because in documents often many screenshots are included and only some important files added as attachments. Then the "Files" tab would be cluttered with screenshots. **Files** tab.
We also <br>
I am not sure I understand everything here correctly. It seems to me that we don't have to be GDPR compliant and remove files from the storage, when functionality yet, that deletes attachments if the user does not want us link to keep them (e.g. deletes the file).
Another important topic attachment is that deleted in the editor. So question 1 is: **Do we want to have document versions in delete attachments automatically from the future. Then multiple versions of a document could include the same attachment.
### There are several options
<br>
1. We list all files "Files" tab (and in the files tab, regardless of how location where they were uploaded. To make it easier for users we could distinguish here between files uploaded in stored), when the editor and files uploaded link to them was removed in the files tab. We do editor?**
Pro:
* We're not delete files when keeping unused attachments so less clutter for the user removes the link in the document text.
Pro:
- We are easily able to provide
* GDPR complicance? Is this a "delete" link topic for each attachment (although we probably should warn the user that?
Contra:
* It might be unexpected for users when the file is still used attachments are completely removed just by removing them in the document or a document version) and are GDPR compliant with this.
- Easy editor
* Sometimes people maybe just want to implement
Contra:
- Maybe cluttered view?
- Users could forget they have to manually remove change the file after they deleted structure of the link to the file in the document
<br>
2. In the "Files" tab therefore removing files only temporary. If they don't have them at hand for re-upload we only list files make that were uploaded in the "Files" tab and ignore all files that were uploaded in the editor.
Pro:
- harder.
* Probably nicer for users, less clutter on large documents
Contra:
- We somehow need hard to know implement, especially when the last occurrence of a link to a file was deleted from a we have document (and in versions.
If the future also from the document versions) so answer is that we can automatically delete it to be compliant with GDPR. This could be complicated and probably slow want that, question 2 would be: **Do we need that functionality for huge documents with many versions => high implementation effort and maybe bad performance
V1 of the collaborative documents?**
As always, please feel free to edit and add options, pros and contras more arguments or questions as you see fit.
First: We need
### Current state
In the **classic documents** module, there is no difference between
In **work packages**, inline attachments (uploaded with CKEditor), e.g. images,
However, files that have been added to a **comment to a work package**, are
Wieland argued, that it would be nice for users to distinguish between inline attachments
We also
I am not sure I understand everything here correctly. It seems to me that we don't
Another important topic
### There are several options
<br>
1. We list all files
Pro:
* We're
Pro:
- We are easily able to provide
* GDPR complicance? Is this
Contra:
* It might be unexpected for users
- Easy
* Sometimes people maybe just want
Contra:
- Maybe cluttered view?
- Users could forget they have to manually remove
<br>
2. In the "Files" tab
Pro:
-
*
Contra:
- We somehow need
If