At the moment the following is supported:

• Ability to add custom group actions by defining a form page and an action page and adding them to the configuration.
• Ability to set some of the native fields.
• Ability to set custom fields.

Please provide the list of the native fields that you think are worse providing group actions for. Also should these be bundled in a certain way? For example, at the moment we allow setting the "Fixed in Release" and "Resolution" field as part of the "Resolve" action.

When I choose multiple issues (by checking their checkboxes) I can do a few actions on these issues (like resolve them, close them etc etc).
What we need to do – is to make sure every access level (like tester, developer etc.) will be allowed to do any action on any amount of issues by not accessing the issues at all (only by checking them and selecting the action below).
Of course, we need to make sure - that testers will be able to do only testers actions, Managers will only be able to do Managers actions etc.

Can do it ourselves (if this is configurable) or (if this is not configurable) to implement it as a feature ?

Note that the available actions may change based on the current project: All Projects, ProjectA, ProjectB, etc. It may also change based on the current user's access level.

Actions that are currently supported:

• Move
• Copy
• Assign
• Delete
• Resolve
• Set/Unset Sticky
• Update Priority
• Update Status
• Update Category
• Update View Status
• Update Fixed in Version
• Update Target Version
• Update <custom field> (entry per custom field).

Actions that may make sense to add:

• Add a note?
• Monitor
• Unmonitor
• Change Reporter
• Update Reproducibility

This feature request was split into two child items and they were both done.