How to filter users manager from user asset object

[JZD]

Hi Folks 

I have some issue to add the users manager as approver in the issue the user opened. I found here some guides and be trying some hours but have no lock. My situation looks the following:

• Object schema named: Employees
• Object type in Employees Schema Tree named: Employees
  • Department (but not necessary in this case)
  • Role (but not necessary in this case)
• Object attribute in user object for the Manager named: Manager Name
  • Manager Name is directly included in each users object so i have not an extra object in my employees schema tree

have tried already from this guides:

Finding managers of users and setting them as approvers automatically - Web Site - Confluence

How to auto-populate approvers from Asset objects attributes using automation in Assets | Jira | Atlassian Documentation

My automation looks actually:

my workflow for the approver is in place but in this case i need to use for each request the users manager to add him as approver.

From my automation the first part til and with extracting the reporters email address is working fine. The Audit log shows each time an success but the manager (i think) is not found and not entered in the issue as approver.

Thank you in advance

[Bob Dalm · Accepted solution]

Hi JZD, 

You'll need to fill the user picker field with the accountId of a Jira user. Looking at your screens this would be something along 

{{lookupObjects.Manager Name.Atlassian Account ID.accountId}}

As Valerie rightfully suggests, get the input values in a Log action, so you can review what happens in your rule's audit log. 

Best regards, 

Bob

[JZD]

@Bob Dalm Thank you man, you are my hero :)

I was searching for this multiple hours and i have so much issues to understand how this is working.

{{lookupObjects.Manager Name.Atlassian Account ID.accountId}} is correct!!!! :)

Could i ask you if you can break down to me this smart value

or maybe i try and you can correct me if i am wrong.

1. Starting from the automation where i am looking for the reporters email address
2. here i am unsure, with the compare, what i am comparing? the reporter or the reporters email address for existing
3. {{lookupObjects.Manager Name.Atlassian Account ID.accountId}}
   
   1. lookupObjects.Manager Name = the attribute for the reporters "Manager Name"
   2. lookupObjects.Manager Name.Atlassian Account ID = Managers Atlassian Account ID?
   3. lookupObjects.Manager Name.Atlassian Account ID.accountId = no clue what this is doing

[Bob Dalm]

1. Starting from the automation where i am looking for the reporters email address
   • There would be other ways to do this, but yes!
2. here i am unsure, with the compare, what i am comparing? the reporter or the reporters email address for existing
   • In the compare you ensure there's a result (in fact, that there'is 1 result - this means the rule will fail if there's multiple users with the same email address)
3. {{lookupObjects.Manager Name.Atlassian Account ID.accountId}}
   
   1. lookupObjects.Manager Name = the attribute for the reporters "Manager Name"
      • Exactly, also being an employee object. 
   2. lookupObjects.Manager Name.Atlassian Account ID = Managers Atlassian Account ID?
      • You've named the attribute that contains the Atlassian user "Atlassian Account ID". Simply refering to another attribute (of the object that's in the manager name attribute). Yes, it get's a bit confusing here :)
        
   3. lookupObjects.Manager Name.Atlassian Account ID.accountId = no clue what this is doing
      • so in the "Atlassian Account ID" attribute you actually have an Atlassian user. From this Atlassian user, you want to get the accountId, as this is what's expected for the user picker field as input. 

Hope this helps clarify things a little!

[JZD]

Thank you for your explanation.

Could i ask you how you would solve it with the reporter email adress or how you will do this automation?
I always prefere it simple as possible for the solutions and i from my side think it should be easier as my automation.

[Bob Dalm]

Should be as straightforward as a lookup on

"Atlassian Account ID" = {{reporter}} 

[JZD]

Thank you Bob. Will try it.

[Valerie Knapp · Accepted solution]

Hi @JZD , thanks for your post.

Please can you try putting a 'log' action before the 'edit issue' action and put the smart value you want to populate the edit issue action with? 

When you try to run the rule again and check in the audit log, you should be able to verify if the correct value is being 'printed' into the log and then, if it's not, then we can try to understand why.

Thanks

[JZD]

@Valerie Knapp Thank you very much for your answer

I tried now with the log action but receive no output from my value except the mail address in the first step

[Bob Dalm]

Breakup your smart value to troubleshoot, i.e. {{lookupObjects}} then {{lookupObjects.Manager}} then {{lookupObjects.Manager.Employee Name}}, but also have a look at my comment above :)

[JZD]

Thank you Valerie also for your help. 
I am using not the log action for find other outputs i need to proceed with my automation.