How do you increase the bulk change maximum ?

[Gary Sherman]

I need to delete several thousand tickets and want to increase the bulk change maximum number. I believe this is a configurable field enbedded in an xml file. Does anyone know how do do this?

Thank you in advance.

[MatthewC · Accepted solution]

if you look in the Jira install directory you want to edit the file atlassian-jira\WEB-INF\classes\jira-application.properties (file has moved in newer versions, please see: https://confluence.atlassian.com/display/JIRAKB/How+to+edit+the+jira-config.properties+file)

You want to modify the following section:

# Limits the number of issues that may be edited via a bulk operation in one go.

# This may be useful if you are experiencing performance issues due to a large number of concurrent edits of

# large number of issues. Please note that this should NOT be used to disable bulk edit operations. Use the

# Global 'Bulk Change' permission accessible via the Admin interface in JIRA to do this.

# If a user tries to edit more than the provided number of issues here, an error will be displayed.

# Set the count to a negative number (-1) or simply comment out this property for unlimited number of issues.

jira.bulk.edit.limit.issue.count = 1000

Just be aware that there is a limit for a reason & there will be a significant performance hit. You will need to restart Jira for this to take effect.

[MatthewC]

I'd probably agree & there are lots of small things that should be available through the UI & should not require a service restart to change a parameter but that's Jira for you.

Also in a shared environment that are considerations about resource usage, if you could send your Jira CPU usage through the roof, it could have knock-on effects on other instances

[Deleted user]

This is great, but shouldn't there be a way to configure this on the UI? I mean for a Studio user, it boils down to probably raising a ticket to support for even this small change. And i'm not sure if that can be done as well as it might affect others.

[hitesh kumar dewangan]

How do you do this in JIRA cloud?

[Deleted user]

Has anyone changed the 1000 limit to higher number and can post actual results of any performance hit? If so can you describe is the performance hit was in general (even when no bulk action was performed) or only when bulk action was performed?

[Piotr Pawel Ptaszynski]

I have tried to edit instead of above mentioned file different file:

location: $Jira_installation_dir/atlassian-jira/WEB-INF/classes/
file: jpm.xml
parameter: jira.bulk.edit.limit.issue.count

It worked on making the number greater (and visible from Jira itself) but did not help us with massive delete of 100.000 issues. I have created support case for this. I'll let know once I get response.

[Saurabh Gupta]

Any update

[Sylvain Leduc]

Hello,

for the other guest checking this post, I guess he solved that by increasing the value also in tomcat cfg file, as by default tomcat only allow 10.000 issues max.

https://confluence.atlassian.com/jirakb/bulk-editing-more-than-10000-issues-will-result-in-xsrf-security-token-missing-961791994.html

cheers

[Piotr Pawel Ptaszynski]

It seems not working in Jira 5.1 Any update please?

[Boris Berenberg]

This is because the location of the file has moved. Please take a look at https://confluence.atlassian.com/display/JIRAKB/How+to+edit+the+jira-config.properties+file to see where the file should be located in newer versions