User Updater

Do bulk update to user accounts and profiles in JIRA

X

Create Accounts

X

Update Profiles

X

Replace Profiles

 

User updater for JIRA is a plugin provided by Nemetschek Bulgaria.

We do not have any access to any of the client’s content and Nemetschek will always use appropriate administrative, technical and security measures to protect client’s information.

Atlassian Marketplace

Data Security and Privacy Statement

Data Storage

User updater for JIRA do not store data outside of the JIRA Server. All the content handled by our plugin is stored directly into the JIRA server instance as we don't store user sensitive data. At times, we may temporary store (cache) some configuration information required for the operation of the applications. For license validation, we only store client information provided and generated by Atlassian for that purpose.

People and Access

Our plugin applications have limited access to customer data and such access is programmatically negotiated during the installation. The applications only access the information required for providing its functionality and only data generated by our applications may be temporary retained by our applications for caching and synchronization purposes only. Our plugin applications are designed to allow application data to be accessible only with appropriate credentials, such that one customer cannot access another customer's data. Our plugin support team do not have access to customer data.

Third Parties

We do not use external services.

Privacy

Nemetschek Bulgaria understands and is committed to the the importance of ensuring the privacy of your personally identifiable information.

User's Guide

General Info

To access the plugin you should have administrative right. The plugin is located in "Administration" under the "User Management" .

User profile updater lets you perform several types of bulk operations on Jira users and their personal profiles including user renaming. The input users data is loaded from a file. To assure execution using the expected input you will be prompted to confirm the selected action. When the action is completed you'll see a report with the results of the execution.

 

Create Users:

Available actions in this tab:

  • Create Users - Create users accounts (if it doesn't exist) for each user from the input data

Users list is provided by a file - upload a file matching the file format description (txt, csv or xml).

 

Update User profiles:

Available actions in this tab:

  • Change username - changes the Jira usernames
  • Rename users - changes the Jira users name
  • Activate users - activates the users that were previously deactivated.
  • Deactivate users - deactivates the users from Jira
  • Remove group memberships - removes the group memberships of the users
  • Add group memberships - add the group memberships of the users
  • Remove project role - Removes the project role of the users
  • Add project role - Adds the project role of the users
  • Delete users - deletes the users from Jira if possible (Active Directory users can't be deleted from Jira)

Users list is provided by a file - upload a file matching the file format description (txt, csv or xml).

 

Replace users info:

Available actions in this tab:

  • Replace users info - replaces the user profile properties including user name with the information provided in the uploaded file.

Users list is provided by a file - upload a file matching the file format description (txt, csv or xml).

 

User properties

All file formats support the following properties:

One of these properties is required for all actions in Create UsersUpdate User profiles and Replace users info tabs

  • username - the username of the user in Jira
  • email - the email of the user

All of these properties are optional and are used in the Update User profiles tabs.

  • fullname - the full name of the user
  • groups - adds the user to the specified groups (separated by a comma).
  • new_username - the new username that will replace the current username
  • new_name - the new name that will replace the current name 
  • project_roles - adds or remove the user from the specified project roles (separated by a comma).
  • project - the name of the project that the role actors are associated with

This property is required for the action Add or Remove group memberships  in Update User accounts tab.

  • groups - adds or removes the user from the specified groups (separated by a comma).

This property is required for the action Rename users in Update User accounts tab.

  • new_username - the new username that will replace the current username

This property is required for the action Activate or Deactivate users in Update User accounts tab.

  • username - the username to activate or deactivate

This properties are required for the action Add or Remove project roles in Update User accounts tab.

  • project_roles - the specified project roles (separated by a comma).
  • project - the name of the project that the role actors are associated with

File formats

  • TXT - a simple text file (with a .txt extension) containing all properties of the users in the format <property_name>=<property_value> (e.g. email=johndoe@test.com). The username property must be first for each user info and then followed by the other properties for this user, the next username property entry will describe another user:

    username=johndoe
    email=johndoe@test.com
    fullname=John H. Doe
    groups=jira-developers, jira-administrators
    new_username=jackdoe
    new_name=Jack Doe
    project_roles=Developers, Administrators
    project=Demo Project 

     

    username=janedoe
    email=janedoe@test.com
    fullname=Jane H. Doe
    groups=jira-developers, jira-administrators
    new_username=jasminedoe
    new_name=Jasmine Doe
    project_roles=Developers, Administrators
    project=Demo Project 

  • XML - an XML file in the format:

    <users>
    	<user>
    		<username>johndoe</username>
    		<email>johndoe@test.com</email>		
    		<fullname>John H. Doe</fullname> 
    		<groups>jira-developers, jira-administrators</groups>		
    		<new_username>jackdoe</new_username>		
    		<new_name>Jack Doe</new_name>		
    		<project_roles>Developers, Administrators</project_roles>		
    		<project>Demo Project</project>		
    	</user>
    <user> <username>janedoe</username> <email>janedoe@test.com</email> <fullname>Jane H. Doe</fullname>  <groups>jira-developers, jira-administrators</groups> <new_username>jasminedoe</new_username> <new_name>Jasmine Doe</new_name> <project_roles>Developers, Administrators</project_roles> <project>Demo Project</project> </user>
    </users>
  • CSV - a comma-separated values file containing one line per user info separated by commas in the following order: username, email, fullname, groups, new_username, new_name, project_roles, project:

    johndoe,johndoe@test.com,John H. Doe,"jira-developers, jira-administrators",jackdoe,Jack Doe,"Developers, Administrators",Demo Project
    janedoe,janedoe@test.com,Jane G. Doe,"jira-developers, jira-administrators",janedoe,Jasmine Doe,"Developers, Administrators",Demo Project