Cannot bulk archive issues if some properties are added to issues statuses
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A Jira Administrator cannot bulk archive issues. After selecting Archive into the bulk issues features step, the Next button does not appear:
Environment
Any Jira Data Center version from 8.1.0.
Diagnosis
For the issues that can't be bulk archived, take note of:
the workflow associated to them
the status these issues are in
Check the workflows associated to the issues that the Jira user is unable to bulk archive
In the workflow configuration, check if the status (identified in the previous step) is configured with any of the 2 properties listed below:
jira.permission.edit = false
jira.permission.move_issue = false
You can check the screenshot to an example of status that is configured with these 2 properties:
If you see any of these 2 properties, then this KB article is relevant and you can move on to the Solution section
Cause
By default you must be Jira Administrator or Jira System Administrator to be able to bulk archive issues as per Archiving an issue.
However if there is at least one issue that is in a status configured with any of the properties listed below, the Next button won't appear and this is because we explicitly denied for those issues the permission to move or edit them. Such property will apply to all users (including Jira Admin users):
jira.permission.edit = false
jira.permission.move_issue = false
Solution
Edit the Jira workflow for affected issues and modify the properties added to affected statuses to only allow a specific group to edit or move them.
In the example below, such permission will only be given to users who are part of the jira-administrators group:
jira.permission.edit.group=jira-administrators
jira.permission.move_issue.group=jira-administrators
Was this helpful?