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
Our Jira instance has groovy code that assigns values to various UserPicker custom fields.
During workflow transitions, our code essentially does:
ApplicationUser appUser = userManager.getUserByName("username")
This works, but we recently ran into a case where for a particular User it didn't work.
After looking into it, it turns out that what makes this User unique is that he had his username changed through the Jira GUI at some point. For example, if he had been created with "username" and subsequently updated to "username2", the app_user table now looks like this:
jira=> select * from app_user where user_key not like lower_user_name;
id | user_key | lower_user_name
13400 | username | username2
I've verified that the appUser object is correctly retrieved from the userManager, but it seems as though setCustomFieldValue function can't find the right user to set the CF to.
I've also tried updating the CF using the updateValue method, but this seems to have the same problem.
Anyone run into this, and have a workaround?
We're on Jira 7.1.2 FWIW.