...
It’s recommended to deactivate users rather than delete them. If you delete a user it will remove them from the active directory but there may be historical data in the application relating to that user which you want to keep. Deactivating users removes access to Jira and also removes them from the license count so it covers everything you need.
Projects
A Jira Project is a collection of Issues. Depending on which Jira applications have been installed, you may have more than one Project Type available. Optimizer for Jira allows Administrators to perform actions such as
Archiving or restoring selected Projects
Adding multiple users to a to a specific Project Role in multiple Projects
Changing the Category, Permissions Scheme, or Project lead of multiple Projects
Find out more about how to use bulk actions with Projects.
Custom Fields
Jira provides the ability to customize the fields in Issues to meet the needs of your teams. Locking some custom fields can be used to prevent accidental changes which can subsequently break the operation of some Jira applications or plugins. Such fields will be locked automatically but sometimes they need to be manually unlocked to be altered.
Find out how to use Optimizer for Jira to lock or unlock Custom Fields in bulk.
The following table shows all Bulk Actions currently supported by Optimizer for Jira.
Info |
---|
Please note that Archiving is only supported for Jira Data Center and on Jira 8 versions. We are working to re-instate the Archiving feature for Jira 9 versions of Jira Data Center. |
Configuration Element | Actions |
---|---|
Users | Disable Users |
Projects |
|
Project Categories | Delete Project Categories |
Archived Projects | Restore Projects |
Issue Types / Issue Type Schemes | Delete |
Workflows / Workflow Schemes | Delete |
Screens / Screen Schemes / Issue Type Screen Schemes | Delete |
Custom Fields |
|
Statuses | Delete Statuses |
Resolutions | Delete Resolutions |
Notification Schemes / Permission Schemes / Issue Security Schemes | Delete Schemes |