I am trying to set up an automation rule to set assignee to the user who creates a branch in bitbucket.
My rule is shown in the image.
When a branch is created. The user is Automation for Jira and not myself. Why does Jira think at Automation for Jira is the user? Could other automation rules be conflicting with this one?
I'm not quite clear what you see as the problem. Some actions will result in "Automation for Jira" being seen as the user.
Do you have other automation rules which might be creating the branch that is triggering this rule?
If so, then the "Automation for Jira" user is the "User who triggered the event", and would end up as the Assignee.
If that doesn't explain this situation, then perhaps you can clarify what you expect, and what you're seeing. Information from the Audit Log when this rule runs might be helpful too.
Thanks for the reply.
I expect to see myself as the person who created the branch. As I am the one who actually clicked to create branch. There is no automation to create a branch, so it is not Automation for Jira that did so.
This is the Audit Log for the rule to Assign user:
There are a couple of automation rules in place as per the below:
- Add build info adds a comment on the build status
- In Progress on Branch Create transitions the issue to In Progress.
- Auto Assign Test is the one I am asking about.
If one of the first two change the user to Automation for Jira, then how can I work around that? What are the actions that will cause the user to be changed to Automation for Jira, where is that documented?
There's nothing inherent in Automation that will assign an issue. It would be explicit in a rule. So maybe review all the other rules you listed to see if any of them are assigning the issue.
It's also possible to assign an issue as part of the workflow. So you might also want to review the Post Functions in the workflow(s) for anything related to assigning. There are several "Assign to" post functions that could be in play, completely separate from Automation.
I'm not sure what you are trying to say. Your first reply said that some rules cause the user to be seen as Automation for Jira, but not you are saying a user has to be explicitly set in a rule.
There are no other rules that are assigning issues to anyone. This is the first and only rule that has Assign To functionality. No automatic assignments were happening prior to trying this rule.
Post Functions are doing the same thing in that, no assignment was happening but now Automation for Jira is being assigned to. The behavior between automation and Post Functions seems to be identical.
I opened a ticket with support directly for better clarification.
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
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