Hi @Nnaemeka Nwosu - In the Rule Details there is a section for Actor toward the bottom of the screen. It defaults to Automation for Jira which has global permissions. The only time I change that is if the users want something a bit more personal (e.g. When adding a comment, some users want a more relatable name as comment author than Automation for Jira)
Hi @Nnaemeka Nwosu - Sorry I missed that this was for legacy. I'm not sure that you can adjust anything on those automation rules at this point as Atlassian is trying to switch everyone over to the newer automation framework.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My own two cents: I just recreated the three Legacy automation rules in the new Automation system and disabled the old ones. The new one provides much better flexibility (and sanity!) than the Legacy one.
True, except that the new automations are limited per month. And since "update a ticket status when a cutomer replies" uses one of those automations, it means that eventually, if you provide enough service, your helpdesk will just stop updating ticket statuses. I have been debating this with Atlassian for years... for those of us with 5K per month subscriptions, if we have too many clients, we'll just break at some point in the month.
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.