Along with imported users, I need to consider new users being allowed to access our Jira server. A user will need to request setup in our LDAP server. Once in LDAP(which can take several weeks to setup -- big company), the user can log in at any time for the first time and they will be assigned the "jira-users" group. This server has numerous groups defined depending on your job role: hardware designer, software developer, manager, tester, project-mgr, etc. I cannot assign these groups to the user until they have logged in for the first time. This makes for a very reactive rather than proactive setup process.
Some of you might want to suggest setting up the group definitions in LDAP but being in a large company, the wheels that update the LDAP information move too slowly.
In the background link above, it discusses converting a Jira backup XML file and then importing it. I'm wondering if I can generate just enough xml syntax to define a new userid from this LDAP server?
With our corporate setup, I was able to configure the query as Microsoft Active Directory and defined users with unique groups. The queries are automatically and periodically synchronized. Once a user becomes part of a particular group then they show up in Jira. This is the best I can setup.
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