Change Details

Sometime (always?), when you Drag & Drop an Image from your computer to a Workboard Task, the File is not visible to other Task participants. I sincerely don't remember from what moment this happened, but I'm quite sure that this is not a new thing from Phorge. There is an "attach" system. So we attach the File to the Task. So, the File inherits the visibility permissions of the Task. So, the File is automagically visible to persons who can see the Task. Fortunately, the Attach system works perfectly also for Transformed images. If you change permissions of a file, also its Transforms inherits these. So, we make sure that the Workboard image (Transform image) is not generated as an orphan but is always linked to the original file. Before: 1. the original image (mentioned in the Task history) - held default permissions of the File application, so, visible only to the author - if you change their permissions, they don't change the Cover image permissions (super-confusing) - becomes visible tuning its permissions, or, causing a manual attach (but visible only directory, not from Workboard) 2. the Cover image (internal Transform shown from Workboard) - held default permissions of the File application, so, visible only to the author - it was tricky to find that File ID to tune Cover image permissions, maybe easy only for a DBA After: 1. the original image - attached to the Task - so, if you can see the Task, you can see this File and its Transforms 2. the Cover image - it's finally recognized as Transform of the original image - as such, inherits its permissions - so, it's visible to Task participants Closes T15163 Closes T15703

After this change, the cover image is finally always visible to others (people who can see the Task), instead of being visible only to yourself. Example conversation before this change: - Anna: (uploads a nice Cover Image on the Task, using drag & drop from the Workboard) - Bob: Thanks! But I cannot see that image. Please change visibility. - Anna: Ouch! How? - Bob: I don't know. Try Files > your File > Edit > Set Visibility > Something that includes "Bob". - Anna: Done. Do you see my image now? (Spoiler: it's a green pepper) - Bob: Yes and no. I mean, I can see the original file, but not from the Workboard. - Anna: Uh? Have you tried refreshing your cache? - Bob: Yes. Still invisible from Workboard. - Anna: Maybe you have to change Defaults Permissions of the "Files" Application, to have "All Users" - Bob: That is a bit invasive. Let's try. I changed the Files policy globally. Try re-uploading your image again. - Anna: Done. Do you see it now? - Bob: Yes! I can finally see it now, also from the Workboard. Example conversation after this change: - Anna: (uploads a nice Cover Image on the Task, using drag & drop from the Workboard) Done! So, after this change, everything works as expected. Every task participant can see that image, and nobody starts a nonsense conversation, and nobody needs to do random experiments with default application policies. So, after this change: - the original file is attached to the Task - the cover image is not orphan anymore, but mentioned in the "Transforms" of the original file - the cover image so now inherits the original file policies So, Task participants can finally see that cover image (transform), since it comes from a file, and that file is attached to the Task, and since they can see that Task. This change also somehow improves T15768. Closes T15163 Closes T15703

Sometime (always?)After this change, when you Drag & Drop an Image from your computer tothe cover image is finally always visible to others (people who can see the Task), a Workboard Task, the File is notinstead of being visible to other Task participantsonly to yourself. I sincerely don't remember from what moment this happened, but I'm quite sure that this is not a new thing from Phorge.Example conversation before this change: There is an "attach" system.- Anna: (uploads a nice Cover Image on the Task, So we attach the File tousing drag & drop from the Task.Workboard) So,- Bob: Thanks! But I cannot see that image. the File inherits thPlease change visibility permissions of the Task. So, the File is automagically visible to persons who can see the Task. Fortunately,- Anna: Ouch! the Attach system works perfectly also for Transformed images.How? If you change permissions of a file, also its Transforms inherits these. So,- Bob: I don't know. we make sure that the Workboard image (Transform image) is not generatedTry Files > your File > Edit > Set Visibility > Something that includes "Bob". as an orphan but is always linked to the original file. Before: 1.- Anna: Done. Do you see my image now? (Spoiler: it's a green pepper) - Bob: Yes and no. I mean, I can see the original file, the original image (mentioned inbut not from the Task history)Workboard. - held default permissions of the File application, so,- Anna: Uh? visible only to the authorHave you tried refreshing your cache? - if you change their permissions,- Bob: Yes. they don't change the Cover image permissions (super-confusing)Still invisible from Workboard. - becomes visible tuning its p- Anna: Maybe you have to change Defaults Permissions, or, causing a manual attach (but visible only directory of the "Files" Application, not from Workboard)to have "All Users" 2- Bob: That is a bit invasive. Let's try. I changed the Files policy globally. the Cover image (internal Transform shown from Workboard)Try re-uploading your image again. - held default permissions of the File application, so,- Anna: Done. visible only to the authorDo you see it now? - it was tricky to- Bob: Yes! I can find that File ID to tune Cover image permissionsally see it now, maybe easy only for a DBAalso from the Workboard. AExample conversation after: this change: 1- Anna: (uploads a nice Cover Image on the Task, using drag & drop from the Workboard) Done! So, after this change, everything works as expected. the originalEvery task participant can see that image, - attached to the Taskand nobody starts a nonsense conversation, and nobody needs to do random experiments with - sodefault application policies. So, if you can seeafter this change: - the Task, you can see this File and its Transformsoriginal file is attached to the Task 2.- the cover image is not orphan anymore, but mentioned in the Cover image"Transforms" of the original file - it's f- the cover image so now inherits the originally recognized as Transform of the original file policies So, Task participants can finally see that cover image - as such(transform), inherits its permissionssince it comes from a file, - so, it's visible toand that file is attached to the Task, and since they can see that Task participants. This change also somehow improves T15768. Closes T15163 Closes T15703