Matt Stofka
My feedback
188 results found
-
388 votes
An error occurred while saving the comment Matt Stofka
supported this idea
·
-
2 votes
An error occurred while saving the comment Matt Stofka
commented
Agreed! One of our users wanted to schedule a task to go out on the 15th of each month, but it only allows 1st or last day. We'd like to see various options like:
1) Repeat every X day/week/month/year on the X day of the month
AND
2) Repeat every X (Day/Week/Month/Year) on the (First/Second/Third/Fourth/Last) (day of the week)
Matt Stofka
supported this idea
·
-
65 votes
This is still on the roadmap.
Matt Stofka
supported this idea
·
-
2 votesMatt Stofka
supported this idea
·
-
9 votesMatt Stofka
supported this idea
·
-
8 votes
We don’t currently have this slotted in as an update to the Trash page given limited asks for it. If customer demand persists, we will re-evaluate, though this change also requires an API update since https://developer.box.com/v2.0/reference#restore-a-trashed-item only allows choosing of a new target parent folder in the case where the original parent has been deleted or user lost access.
Matt Stofka
supported this idea
·
-
64 votes
Thank you for your input. This idea is considered for future roadmap. Please reach out to me if you like to share your use case.
An error occurred while saving the comment Matt Stofka
commented
Hope this is still under consideration. It's so difficult to identify the correct content to restore as it's quite possible to have multiple items in Trash with the same or similar name. We need to see the folder path from which the item was deleted to determine if it's the correct item to restore AND know which folder it'll be restored to. The current functionality assumes that the user is a single user with no collaborators and isn't part of a business or enterprise where they may have access to many GB or TB of content with often deeply-nested folder paths. So this really needs more attention.
Also, PLEASE REMOVE THE "RESTORE ALL" BUTTON ALTOGETHER. Pretty Please!!!!!
Matt Stofka
supported this idea
·
-
3 votesMatt Stofka
supported this idea
·
-
15 votesMatt Stofka
supported this idea
·
-
2 votes
An error occurred while saving the comment Matt Stofka
commented
This demo that zslavik posted was great...and yeah it's a problem. That "Restore All" button is fine for individual user accounts, but should be eliminated for users on Enterprise Accounts who have access to lots of shared folders and may have many years of deleted items in their trash. It would be an nightmare to fix if an end-user tapped that button.
There's another Pulse thread about removing the "Restore All" function altogether (or my suggestion of allowing Admins to disable it for non-admins):
https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/47031214-remove-the-restore-all-from-the-users-trash-pageMatt Stofka
supported this idea
·
-
3 votes
An error occurred while saving the comment Matt Stofka
commented
Yes, perhaps provide an option in Enterprise Settings to remove the "Restore All" button for end users so that each organization choose what's best for them. I'm waiting for the day that one of our users taps that button and it's going to be an absolute nightmare to fix.
Matt Stofka
supported this idea
·
-
1 voteMatt Stofka
supported this idea
·
-
12 votesMatt Stofka
supported this idea
·
-
2 votes
Not currently planned at this time.
Matt Stofka
supported this idea
·
-
5 votesMatt Stofka
supported this idea
·
-
4 votes
Thank you for this request!
We will review this with additional demand.
Matt Stofka
supported this idea
·
-
58 votesMatt Stofka
supported this idea
·
-
36 votesMatt Stofka
supported this idea
·
-
37 votesMatt Stofka
supported this idea
·
-
2 votesMatt Stofka
supported this idea
·
Glad to see this is on the roadmap finally. External groups would really help with managing access and making it easier to remove external collaborators. Ideally our users would be able to create their own groups or at least allow Admins to create the groups and assign a user to be a group admin without giving them any other co-admin privileges.
Side note: in a closed file structure (i.e., non-admins aren't allowed to create root folders), giving a user any co-admin privileges at all would bypass this so they would be able to create top-level folders. So if you are thinking of making external group management as a co-admin function, please keep this in mind. I wouldn't want them to be actual "co-admins" which would bypass that root folder setting. Hope that makes sense. Thx.