I've recently created a rule to assign/update issue components depending on what is written on its summary. Getting components assigned correctly on all issues is very important to us to, later on, generate metrics for reports.
But our project had been ongoing for quite a while when this rule was created, so many older and resolved issues are now left out. They will not be transitioned further. Is it possible to, using a manual trigger, apply a rule to all issues in a project, or all issues in a project that fit a certain condition?
EDIT: I am using automation pro for Jira Cloud
Thanks for your question. It should be possible, but before I can be certain and offer a solution, can you provide me a screenshot of your rule so far? That will help determine how to figure out a rule to back fill all your old components.
If you're not keen to publicly share your rule, please raise a support ticket with us and I can guide you through it.
Simeon [Automation for Jira]
Thank you for the reply. I think I found a way to do this but ran into throttling issues. The rule is quite large and applies to all issues under the project.
The screenshot below is just the top of the rule, there are 11 branches in total. I changed the scope of each branch from "current issue" to a JQL query selecting all issues in the project for a specific type. That seemed to work but then it reached Jira service limits and did not execute the rule. I'm not sure if there is a more efficient way of doing this :-/
It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event