We would like all users to be able to revise released documents to the next revision in order to make changes, regardless of the owner, owning group, etc.
Currently: The only user who is able to use the revise option to create the next working revision is the original owner (even a DBA cannot revise the item revision). If anyone else tries to revise the released document to the next working revision, they recieve an ACL error. The original owner must revise to the next working revision, then change ownership to the requesting user.
How can I update our system to allow any user to be able to move any item to the next item revision without relying on the original owner?
You would already know, but would like to repeat:
Please do take a back up of your AM Rule tree before you attempt any changes to AM tree.
Coming to your question, it is kind of difficult to guess how your AM Rule tree looks like...so my suggestion (below) will be a shot in the dark.
Here it is:
For released objects, usually 'copy' access needs to be in place to group/role/role in group on say: Has Status() node/condition or Owning Group node/condition or Has Class or Has Type.
Once again there is a need to understand your scenarios to better describe the placement of the above nodes/conditions.
Let us know how it goes.
That is not OOTB behavior. Someone at your site changed the Access Tree to revoke "Copy" privs from the Owning Group. All you have to do is re-grant "Copy" privs to Owning Group.
However, you may want to inquire of your TC admin(s) WHY they did that in the first place. There might be a reason for it.