Hi dear community!
Faced a little question:
After setting up and fully using automatic rules, it turned out that their implementation was limited.
This strained quite a lot, because the whole business process is built on this:(
There is a rule that is triggered after adding a comment. Then there are two conditions, in most cases these conditions do not pass and the rule ends with the status NO ACTIONS PERFORMED.
However, it counts as completion and the limit is reduced. Did anyone manage to set it up so that the limit decreases only from the successful execution of the rule?
Thanks a lot!!
I understand that this can be frustrating that you only want the rule to count towards your limit when an action has been performed.
However from an Atlassian point of view the rule was executed as it was evaluated fully (it was triggered) but it turned out that there was no action needed.
So this does count towards an execution of the rule.
You can always evaluate whether your trigger can be set less broad so it triggers less.
Another one however is to move the rules from "Global/Multi project rules" in to project specific rules.
Normally project specific rules have no execution limits where as Global rules do based on your tier and number of users.
Hello @Dirk Ronsmans
I completely understand your answer. But when a comment is added, there are no other options. Translation of a rule for one project does not affect linked tasks, which in this case will not help automate the process in any way.
From my position, it would be convenient to add several triggers, for example, the "add comment" trigger and immediately the trigger condition.
And of course avoid " no actions performed " in the limit counter
Are you sure that you cannot translate them to single project rules?
As far as i know a single project rule can still interact with other projects/linked issues but the condition is only triggered/monitored for that single project.
Or I misunderstood how you rule is set up :)
@Dirk Ronsmans No, that doesn't work.
For example, the rule starts every 5 minutes, if there are clones that are done, then add a comment. Very simple example, but it should work. No. Nothing for single project. But if we change amount of projects to 2 - this rule work exсellent.
Maybe I'm wrong, but so far I have not been able to achieve at least some result using one project.
I feel like this has be possible with less :)
So if I understand correctly, you want the automation to:
I'm not sure quite what the actual use case is here but if this is based on transitions, it might make more sense to use the issue transitioned trigger. You can filter on that trigger to the destination status that you want.
So, in this case, if a ticket is transitioned to Done, go through its linked issues, etc.
@Simeon Ross Hi Simeon!
The original question was that the trigger fires on every comment, checks the conditions, not finding the desired condition, completes, but the counter also increases.
Instead of one rule, I ended up making 4 rules based on field changes in order to minimize automation for many projects.
And the second question, which we also considered here, is that if the automation is only for one project, it cannot check related applications from other projects.
Automation with status transitions is already configured, thanks:)
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events