Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bulk Change > Edit Issues says I do not have permission

Mark Thornhill
Contributor
February 19, 2018

Hello

I am trying to do a Bulk Change, on a Project that I have done other Bulk Changes on, but on this particular query, I get the message:

NOTE: You do not have permission to edit the selected 183 issues or at least one issue has a status that forbids editing.

next to the Edit issues.

Is there a way of finding out which issue is preventing me from making the changes I want to make?

Thank you

Mark

3 answers

1 accepted

5 votes
Answer accepted
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2018

I think you need to filter issues by a project and then find out which issues cause the problem. There is no easy way.

Mark Thornhill
Contributor
February 20, 2018

Hello

Thank you for your answer.

I did find what was causing the issue, by changing my query, until I had a smaller enough set of issues, I could see where the problem was.

It was quite simple in the end, any issue with a Closed status, stopped the Bulk Change from working.

Like # people like this
Anil Kumar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 26, 2020

Thanks Alexey .. its worked Fine for me .. Thanks a lot

2 votes
Demetris Karacostas
Contributor
July 3, 2023

Another possible cause of this is the following property on a status:

Property Key: jira.issue.editable

Property Value: false

If the above property is defined on a status in your issue workflow, it will prevent any form of editing, including bulk edit.

1 vote
upatec1
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2022

I have one issue in "Archived" status causing this. I changed the status of that issue and it worked.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events