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
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
Jira Issues are linked to Insight Objects 'Organizations'
Each 'Organisation' has an Account Manager attribute (User Lookup)
If the Account Manger is populated and an issue is raised linked to the Organization, how can I automatically assign the Jira Issue to the user / agent named in the 'Account Manager' attribute?
@David Harkins excellent!
This is indeed something that we have configured as a Post function. In my use case we've set the post function immediately on the create transition.
Do you have any experience with pulling data from Insight thru scriptrunner? I'll see if I can get an example script from my environment. (might need to redact some things but the idea remains the same :))
Hello @Dirk Ronsmans
I've not used Scriptrunner for this purpose yet, you could say i'm a newbie.
The issues have an Insight Object custom field which does display the Account Manager name, not sure how to pull this data out yet.
Any samples / guidance you can offer would be appreciated.
Quick question, do you have an Insight custom field defined with the Organization and that Organization has an attribute Account Manager OR is your Account manager an Insight Object in itself on the issue?
That would change the script a bit..
One would mean getting an attribute of an Insight object from a custom field while the other would mean just getting the Insight object
You can easily assign the issue to the Account Manager during a transition (including create) using the built in workflow post function.
I believe you can also do something similar with an Approvers using this workflow post function.
As Dirk mentioned, having the Organization attribute as a user data type makes it easier. I store my users as separate objects, so it's a little more complicated and requires using a bunch of Groovy scripting.
These are workflow post functions, so they'll only fire during a transition. If you want it to transition when the Organization object changes on an issue, it'll require the use of Groovy scripting in either Scriptrunner or Automations.