I have Butler looping on a custom field change - options?

[Deleted user]

I have a looping issue in Butler that can't be resolved unless one of these options were available:

- Some sort of loop break or don't allow a rule to trigger itself

- Allow custom fields to be read-only (and set only by Butler)

- Allow for a rule to trigger off of ANY card change, instead of specific card changes. (This would still cause a loop)

Currently, Butler loops 3 times, recognizes the loop, stops the rule and then posts in the log. I'm ok with that too but Mr. OCD here doesn't want the error cut and the minor performance hit. Any thoughts? (this really comes down to the lack of flexibility with the Custom Fields power-up)

[Ryan]

Hi Peter,

Could you send through the rule that you have set up? Perhaps there is a different way that you could set this up to prevent the loop from occuring.

Thanks,

Ryan

[Deleted user]

Hi Ryan,

when custom field "Card Number" is set, set custom field "Card Number" to "{cardnumber}"

I know exactly why this is looping - bad form on my part, but it was the only way I could prevent users from changing a custom field value that is set from an internal field.

If we could have the option to make a Custom Field read only (or only set by Butler), I can remove the rule.

Thanks :)

[Ryan]

Hi Peter,

Thanks for that information and I can also see why that rule would loop. I agree that the issue is actually around permissions and the ability to edit board content. With our Business Class subscription, you can set a board member's permission to be "Observer" which means they have read-only access to the board which would prevent this.

Would that be an option for you?

Ryan

[Deleted user]

Hi Ryan,

The users on this board (part of Business or Enterprise class) require access to create and edit cards, I just don't want them to touch the Card Number Custom Field. The card number acts as our request number which needs to remain fixed. A read-only custom field would solve this or the ability to hide the custom field from the back of the card but display on the front would solve this as well. I've tried other card number power-ups, but custom fields are the only ones that are included on board export (and our enterprise is only restricted to power-ups provided by Atlassian/Trello)

Peter.