Hi Community,
We have a set of automation rules for 2types of projects when this 2types of projects created in Jira then these set of automation rules should applied to this 2types of projects automatically every time. Is this possible through any scripts?
please help me if there any feasibility.
Thank you
Regards,
Vishnu.
Since you seem to be on a premium plan, why don't you configure them as global automation rules? At worst, you would need to update the scope to of your rules to include additional projects upon creation, but you might even use project categories combined with JQL conditions in your automation rules to overcome that issues as well.
To illustrate my last pointer, if you add your projects of type 1 to e.g. a project category named Type 1 (not very original in my example, I gladly admit) and you have an automation rule that responds to the issue created event in all your type 1 projects, just add a condition to your automation like this:
Hope this helps!
Actually we have limited Automation rule executions. if we set this set of rules globally the execution limit will breached after some time that's the reason we exploring other ways.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is there any add-on for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to make sure: you indicated you are on a premium plan on your question here. If that is true, you have 1,000 global rule executions per month x the number of users you have (i.e. if you have 200 users, that would grant you 200,000 (global) rule executions per month. That's really a lot, just to give you some perspective there ...
If you still feel you should clone your automation rules separately, you can export your automation rules in json format from the global automation overview page. You can use that json file to import those rules again. During import you will be asked to map your rules to a project, which may be your new project.
That may already save you some time, but be aware that you still have to review the rules to make sure they don't fail on some project-specific pieces of configuration in them.
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.