Hi there, is it possible to quickly duplicate rules or buttons? I’m finding I am repeating similar rules and would be great to be able to duplicate existing rules.

Released today [image] August 29, 2024 / Linear integration, Duplicate Rule or Button, Restrictions to work with Fibery from Russia Changelog no_entry_sign Restrictions for customers based in Russia (and some other countries) The U.S. government has introduced restrictions prohibiting access to certain software products and services to any person in Russia. Due to these restrictions, Fibery will no longer provide users located in Russia access to the platform. It will be not possible to register new accounts if you are accessing Fibery from Russia starting September 1st. It will be not possible to access any Fibery account from Ru…

Yas, I want this so bad. I am using a script to check rich text description fields every hour and then give me an icon if it contains anything, and I’d LOVE to just use it for ALL databases with a quick copy/paste sort of action (a batch add would be ideal, but baby steps for now lol), but having to manually re-type it for all of them has made me abandon it for most databases.

I was actually thinking that being able to define “templates” might be a good way of achieving this. That way you can have a centralized location to manage some frequently used automations. If there was a way of updating all automations based on the same template, but still keep the customized parameters, that would be the icing on the cake :grin:

Related: Centralized script management for Workspace

Hmm, do we need a proper feature request for the creation of a central place to manage Automations + Buttons? Being able to Duplicate would be helpful within a given Database, of course, but even better would be if there was a central location where you could e.g. copy an Automation from one DB to another, either with a guided remapping process for the fields in the Automation, or just redoing it manually through the regular editor afterward. Of course you could just have the Duplicate function requested here allow for you to specify a different DB, but I think sooner or later having a central location with e.g. filters to look at individual DB’s automations, will become important and valuable.

[image] Oshyan: do we need a proper feature request for the creation of a central place to manage Automations + Buttons? Probably :wink: The closest I could find was this: [image] Centralized script management for Workspace Ideas & Features When you have 30+ bits of javascript scattered among dozens of Rules and Buttons in a dozen Spaces, managing this codebase becomes a nightmare scream. If a Space or DB gets renamed, or if a DB gets moved from one Space to another, scripts break. We really need a more robust way to manage a Workspace’s codebase of scripts - a single place where we can: See everywhere scripts are defined: Space > DB > Button/Rule > Action Perform global search-and-replace on all our scripts (or scripts defi…

[image] Chr1sG: The closest I could find was this: Right, exactly… @Matt_Blais do you think your feature request there makes sense to expand to a general cross-DB library for automations and scripts? Or should a separate one be made?

[image] Oshyan: do you think your feature request there makes sense to expand to a general cross-DB library for automations and scripts? YES - I think the more we can consolidate the various aspects of “Script/Automation Management” into one feature, the more powerful it will ultimately be. Of course the downside is, the bigger your ask, the longer it will probably take. :cry:

[image] Matt_Blais: Of course the downside is, the bigger your ask, the longer it will probably take. :cry: Well… yes and no, or perhaps I should say… maybe. This is not always true, but consider this: in the case of your particular feature request, I would argue that it may be niche enough as to quite honestly not be something that would be prioritized in any foreseeable future. That is not to say it’s not a good idea, valuable to you and some other people who are heavy script users. But I suspect the number of people it might help is less than 20% of Fibery users. That might be a tough sell for the dev team. Especially if developing the “library” concept is a similar amount of work for that vs. a more broad library that also encompasses Automations (that’s speculative on my part, and clearly it would be some more work to add automations in there). Anyway, that’s a long-winded way of saying that, while expanding the scope might make it take a bit longer, it could also make it a more broadly beneficial feature request that could garner additional support from the larger percentage of users it may benefit, and also make it easier for the dev team to prioritize. Perhaps… :grin: I have the ability to edit your Title but not the body text of your Topic. So would you like to go ahead and change it to expand the scope (both in Title and Body/Description)?

[image] Matt_Blais: I think the more we can consolidate the various aspects of [insert request] into one feature, the more powerful it will ultimately be I think this is an important point. I think there has been a push and pull in the forum to keep the ideas somewhat specific and break out variation or extensions of ideas into new requests. I think the main point has been to be able to measure support for specific ideas through votes as well as be able to provide feedback to the community on status of each idea (since the team likely will only tackle only a subset of a bigger idea). However, I think this actually leads to fragmentation and duplication of a lot of similar ideas. So instead of building on top of each other’s ideas and needs, we end up creating separate streams and discussions. @Oshyan , @Matt_Blais and @Chr1sG have been doing an excellent job of linking related items together. However, I’m hoping we can find a better way of breaking down larger ideas and tracking them and allow the discussions in the community to be “additive”. I think as the Fibery becomes more feature rich on the public side, we can hopefully leverage Fibery itself to make this possible.

If I could provide my 2 cents. I would be slightly disappointed if this got rolled up into a larger feature to do with templating or scripting or similar. This request (in my mind) is a simple button to be able to duplicate a single rule so I don’t have to recreate it from scratch with a slight variation.

[DONE] Duplicate automations

Ideas & Features

mdubakov August 29, 2024, 2:21pm 15

Released today

Topic		Replies	Views
[DONE] Copy existing rules Ideas & Features automations	12	813	January 8, 2026
Duplicate an automation [DONE] Misc	2	201	October 4, 2024
Centralized script management for Workspace Ideas & Features automations	7	1948	February 28, 2025
Allow drag-drop sorting Rules (similar to drag-drop sorting of Access Templates) [DONE] Ideas & Features	9	351	October 4, 2024
🧐 Your opinion needed. Automations in Fibery (limitations and opportunities) News & Announcements	76	1854	May 21, 2026

[DONE] Duplicate automations

Related topics