I created an custom option field which is updated by an listener. To avid editing, the field is removed from all edit screens, at last for the relevant projects. So the field can't be edit manually, which works fine.
In bulk update after an search I do can select the field for updating, even if the issues belong to an project which can't edit it.
How can I avoid the update possibility in the bulk update?
@Alexey Matveev _cPrime_it's not an admin feature
To perform a bulk operation, you'll need the appropriate project-specific permission and the global Bulk Change permission. For example, you would need to have both the Move Issue and Bulk Change permissions to perform the Bulk Move operation.
@Thomas Strohmaiermaybe you could do it by cutomization of the template file of bulk edit
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event