You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When a customer replies to a question, the status changes from Waiting for customer to Waiting for support. So far so good.
What I don't like is that it says I made the update. The history says "Emma Ivarsson changed the Status" and so does the email to the client. It looks like I'm tampering with the tickets.
How can I remove my name from this automated status change?
Found the setting after having been pointed to How to change the "person" that triggered events s... (atlassian.com)
HI @Emma Ivarsson - The automation rule actor (set in the Rule Details) should be set to something generic like Automation for Jira
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.
Unless your environment is using a marketplace add-on, automatically transitioning an issue would be done through Jira automation. You should be able to see what automations are on your project here:
https://YOURINSTANCE.atlassian.net/jira/software/c/projects/YOURPROJECTKEY/settings/automate#
You may not have created the rule, but perhaps someone created one on your behalf?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't find any automation rules of the sort, but this is in the workflow:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apologies - Just re-read the question. You're talking specifically about the history of the status change. Not a specific comment being added automatically.
Since you're the one transitioning the issue, it will in fact show you in the history. There are a couple options:
I hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The thing is, it isn't me. I set up the project and I am the project lead, but I'm not working on the tickets at all. That's why it looks so odd in the tickets and emails. Alice and Bob are discussing an issue but this chick named Emma keeps changing the status back and forth.
I'm thankful for the suggestions but they don't work. I want the statuses to be clear to the customers and I want everyone to use their real names for traceability.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh interesting. That takes me back to automation. There has to be something there that is transitioning the issues with your account. Automation is the only explanation. Are you the Jira Admin for your instance? If not, it is possible that the Jira Admin set something up as a global rule under your name. The big thing is that there is an automation rule configured somewhere and for some odd reason, your account is set as the actor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am one of the admins. I guess one of the other admins could have set up something in my name but it seems unlikely. There could of course be a rule that is run by "project owner" or something. I'll ask around.
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.
Thank you, @Emma Ivarsson! We were also experiencing this weirdness - regardless of who responded to a ticket, it looked like our CIO was updating the statuses.
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.