I am looking to solve an issue..
We currently have the following:
I don't want to use Atlassian account. Instead I want to use the email of the reporter for example.
How do we get the reporter e-mail through a placeholder to use on an AQL?
Regards
Howard
Hi Howard!
Long time, no see :-)
Have you tried:
${reporter.emailAddress}
Regards,
Jeroen
Hi @Jeroen Poismans ,
Great to hear from you!
I tried that, it does not load the objects as soon as I change it to:
object HAVING inboundReferences("Atlassian Account" =${reporter.emailAddress})
Or would you approach the Filter Issue Scope differently?
Cheers for replying.
Regards
Howard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you provide me with some details:
Regards,
Jeroen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Of course.
Goal:
Users Accounts (Object) in assets and in JSM need to be mapped to display relevant values in some dropdowns to the current user (customer portal). How this matching should be done? Atlassian account VS email? All users in both Jira & Assets in our context are expected to be present in both side and thus the matching with email adress should be sufficient and adding the Atlassian account shouldn't be required.
So these are the objects within the object schema:
Zooming into the User Accounts Object (which are users/customers):
Now, Atlassian Account is an Attribute of the object User Accounts:
Here is an object graph for an user account:
Hope that gives the required details. To be fair, the more and more I investigate it looks like the placeholder for email can't be used in an AQL.
Regards,
Howard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Accounts OT (not the User Accounts), does it have a link to User Accounts?
In other words, is User Account present as attribute on the Accounts OT?
Jeroen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are the attributes for Accounts:
ObGraph:
InboundRef for Accounts:
So, as far as I can grasp :), these are objects referring to each other.
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.