Restrict bulk change issues for users

[Nag]

Hi Support,

Few users are making mistakes while editing issues in bulk like
1. Changing summary for multiple issues
2. Changing description
3. Changing field values etc

So we would like to restrict the users to edit issues in bulk but in individual they should be able to edit. 

We would really appreciate if you have any suggestions.

Many Thanks,
Redy

[Joe Pitt]

You need to remove the bulk change permission from the users

https://confluence.atlassian.com/adminjiraserver073/managing-global-permissions-861253290.html 

[Nag]

I really appreciate for the quick response Joe Pitt.

Still I have a question. With this option I can remove all the jira-software-users how ever I need to allow Project admins to bulk edit.

Can we add the project roles in global permissions? or is there any way that project admins can have bulk edit capability?

Please advise.

[Joe Pitt]

I would create a group called bulk change and put the project admins in the group. Then remove any other group from the bulk change permission and add the bulk change group

[Nic Brough -Adaptavist-]

Put the admins in a new group, add that group to the global permission for bulk edit.

[Nag]

Thank you Joe and Nic, I had same thought in mind.

• Again this is going to manually added admins to the group every time new projects created.
• User may be admin in one project and just user in other project. If we add users in the Bulk edit group then they'll have permissions in those projects.

Please advise.

[Nic Brough -Adaptavist-]

You either give them bulk-edit or you do not.  It's not a project permission, it is global.

[Jeff Wilson]

@Joe Pitt  @Nic Brough -Adaptavist- 

Is it possible to limit bulk edit actions?  I want to grant someone the ability to edit in bulk, but I don't want them to be able to delete through bulk edit.  Is that possible?  We want to limit delete function to just admins, but it seems bulk edit gives them access to that function.

Thanks,

Jeff

[Joe Pitt]

Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.

Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.

The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.

That said, I wouldn't think edit would allow delete as they are different permissions. I don't allow ANYONE to delete so I would never have seen that option. 

[Jeff Wilson]

Thank you for the quick reply.  As and admin I am able to delete issues in Bulk Edit mode.  A lot of it has been clean up work because tickets were entered too soon and they weren't needed after a new direction was taken.  But I hear your warning and will look to handle this differently in the future.  That actually may resolve my concern. 

however, the Delete feature is part of the Bulk Edit.  how do I turn it off.  even for myself as an admin?

[Joe Pitt]

You need to remove your delete permission. 

[Joshua Sisk]

Surprised there is seemingly not an easy way to create a group for all Project Admins that stays updated. We'd like to let all Project Admins to have bulk change permission - is there a way to do that doesn't involve manually adding them to a group whenever there are new projects created with new admins?