Steps to reproduce for v3.3.10 :

• Create user TEST_USER that can only edit Content having Object State Not Locked
  (see policies-not-locked-content.PNG)
• Try to create a new Content Object ('Folder' for example) as TEST_USER

 Result:

• User is not able to edit and save the Content Object
  (see create-folder.PNG)

Expected Result:

• As a new Content Object after saving has by default the Object State Not Locked, the User should be able to create Content

----

Steps to reproduce  for v2.5.24.1 :

• Create user TEST_USER that can only edit Content having Object State Not Locked
• Create a new Content Object ('Folder' for example) as TEST_USER and save the Content (do not publish)
• Go to Dashboard and try to edit the new draft

Result:

• User is not able to edit the Draft.
  Notification Bar shows error: "You don't have permission to edit the content"

Expected Result:

• User should be able to edit the Content, that he just created.

----

Note 1:
Custom implementations might require to change the Object State before the Content Object is published for the first time. A fix should have this in mind, if possible.

Note 2 (for 3.x):
Additionaly - as seen in create-folder.PNG - "publish later" button should not be active when user is is not allowed to publish. This will be added in a separate ticket though.