[CONTLOCK-6] Publishing fails when sub node is locked Created: 11/May/23 Updated: 23/May/23 Resolved: 23/May/23 |
|
| Status: | Closed |
| Project: | Content Locking |
| Component/s: | None |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Sonali Raulo | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: | |
| Start Date: | |
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
| Comments |
| Comment by Richard Gange [ 23/May/23 ] |
|
It's not practical for me to rewrite publishing actions to consider locking. It's a hard lock for all users. It's expected that publishing would fail since publishing would be trying to change the node's metadata. |