You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
How to stop staff from renaming and deleting lists?
@Jackie Daniel there is no way to do this built in, but you can put in *some* protection using the API.
The most bulletproof way I have done this in the past is with 2 API functions:
1) When a list is archived, unarchive the list
2) When a list name is changed, find a card in the "Board Definition" board named with the list id and set the list name to the description of the found card
3) When a list is created, create a card in the "Board Definition" board named with the list ID and set the description to the name of the list
4) When a list is created, create a list in the "Board Definition" board in the same relative position as the created list
5) When a list is moved, find a list with the same name in the "Board Definition" board and set the relative position of the list to match that of the found list
What this means is that every time you create a list, a "definition" is created that holds the name of the list in its description. After you do that, you can only change the name of the list by updating the description of the corresponding definition card, otherwise anytime the list name is changed, it will change back to what it was originally.
This can't protect against someone moving lists to another board where the "bot user" doesn't have access. Any user of your board could maliciously create a board no-one else has access to, move the list to it, then delete that board. To protect against this, you need something like Rewind to do backups against data loss, but the above will protect against people kind of inadvertently screwing things up by renaming lists or moving things around in the course of their normal work (ie. not malicious behaviour, but "bull in a china shop" type behaviour).
We can create these API automations relatively inexpensively using our BenkoBot platform:
You could also create a rule to send you an email when a list is re-named or archived and tell you who did it, then you can contact them and ahem- politely ask them -ahem to stop doing that, and make it their responsibility to put the list back the way it was ;]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jackie Daniel 👋
Welcome to the Community! There are a number of permissions you can set on a board depending on the user, I'd recommend reading Trello's guide on changing permissions on a board.
I hope this helps but if you have any other questions just ask away 😃
All the best,
Laura
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They need to be able to comment and move cards to completed list but NOT MESS them up and rename header titles of lists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeah pretty silly that this isn't possible and that the articles are not help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.