I have browsed through many threads relating this issue, but haven't found a helpful solution to my problem.
I was asked by the system to start using automation. I definitely see the potential of automation, and I created my first rule.
I see that it fires, but no changes occur.
Many of the threads with potential answers were written a long time ago and screenshots no longer resemble current screens. But many users seemed to have an issue with assigning the atlassian-addons-project-access role to the project.
So I can see the role in the system:
And I can make the role owner and actor of my automation rules
But somehow, when I perform the action that should fire the rule, the rule gets fired but nothing changes. It should change the start date of a "blocked" issue when I change the due date of the related "blocked by" issue.
Can someone help me?
Hi Tijs,
could you provide a screenshot of the settings in your action and the automation rule log entry?
Hi @Tijs Tijert
Adding to Lisa's suggestion:
The automation rule's Owner defaults to the person/user in Jira who created the rule. I have not seen anyone assign that to the automation user before. The value of having this be a person is that when something goes wrong with the rule, the automation engine will email that person of the problem/error so they can take action.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lisa and Bill,
I have changed the owner to myself, changed the setting so that I get informed whenever the rule fails and tried again... I got no email, the rule triggered, but no start dates on other issues where modified.
Attached is a listing of the complete rule settings. I have tried to find where to get a rule log entry, but don't know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tijs Tijert
I note that the direction of the "blocking" in your condition and your branch are different. Is that intentional?
And, if you check your audit log, that may make it more clear where the processing is stopping.
Thanks,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill, thanks for your time with this.
About your remark about the blocking direction.... I assumed that would be needed this way, because the original issue has a link of the type "blocks".
But when you open the related issue, you see the same link, but now with type: "Blocked by"... I will try to set the same direction on both and see what's happening.
But can you tell me where to find the audit log?
I was looking for it but didn't find it "yet".
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.
Succes! That was it! I think it's a bit dubious from a logical point of view, but my rule fired successfully after I changed the "Blocked by" to "Blocked" in my branche.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.