Dear Jira community,
I am not able to run a automation to set a component to issues created via email-handler.
What I do is to set a specific default user for incoming issues via mail. Then my automation sets a component to every ticket which is having the reporter which I chose for issues from emails.
The problem which appears is, that after the component has been set automatically, this process is been undone right after.
Does anyone have an idea where that comes from and how to fix it? There is no other automations which interfer.
Thanks in advance
Hi @Alexander Güth and welcome to the community,
What the history of any of that issue states? Can you post a screenshot here?
What about the rule audit log?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you also share what is on the "Edit" of your rule?
And in addition, fo to cog > system > global automation and see if there are any other rules running, except that specific one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, but could you show us the history of the issue?
We want to see where the component gets added, and then where it gets removed. (There is no "undo" in Jira, it is another change that puts the data back where it was)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alex Koxaras _Relational_ There is no other automation in the global automations.
@Nic Brough -Adaptavist- I added a screenshot of the history in my last reply.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, sorry, yes, you did give us the history. I didn't see it for some reason.
However, that is perfectly clear - you have an automation that is clearing the component after the one you have shown us has set it. As Alex says, this could be a project or a global automation, but it definitely exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes now I see it, there is an old automation which has been modified.
Could have come to my mind, but thanks for your help guys!
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.