Description of problem:

When a locked report template is cloned using Hammer, the cloned template remains locked.
However, when the same locked report template is cloned via the Web UI, the cloned template is created in an unlocked state.

For consistency and usability, cloning a template (regardless of method) should result in an unlocked template.

How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

• Identify an existing locked report template.

• Clone the template using Hammer:

Actual behavior:
The cloned report template is created as locked when cloned via Hammer.

Expected behavior:
The cloned report template should be unlocked,

Business Impact / Additional info:

• Users must manually unlock templates cloned via Hammer.

• Inconsistent behavior between Hammer CLI and UI.

• Affects automation and scripting workflows.