I'm in the middle of transferring my users and issues from our existing 4.4.3 Jira server(Ottawa) to a new 5.2.2 server in Sweden. I have three majors issues to address:
The first two cases are being handled well. With the third case, I have noticed that the converted userids have no LDAP data (i.e. like their full name) until the user logs in for the first time. I'm assuming it is a caching issue. I need the LDAP info like their real full names else problems will arise especially when searching for issues. i.e. I know a person's full name but with their associated userid is not always obvious.
Question#1: How can I force Jira to update its LDAP cache for the 180 users that were part of the existing import without having all of them log in for the first time?
I really don't want to send out a broadcast email giving some lame excuse to log into the new Jira site. As well, most of the users will still ignore the email until they really need to log into Jira for the first time.
Any ideas, thanks Brent
Your question is so thoroughly written, that I am hesitating to write my (out of head) thoughts ;-)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs