[CONTEDIT-175] Tagging blocks for reuse Created: 20/Mar/18 Updated: 04/Apr/23 Resolved: 04/Apr/23 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Team: | |||||||||
| Description |
|
Support tagging of individual blocks in a story. This allows the author to designate a particular block as the socially shareable text or as the summary. Problem: The ability to move blocks around provides great flexibility for authors. But it also makes consuming blocks over REST unpredictable. The "first block" is not necessarily the best summary of the story or the best tweetable moment. Authors have no control over what blocks are used when the story is reused in different channels. User stories:
Acceptance criteria:
|
| Comments |
| Comment by Laura Delnevo [ 04/Apr/23 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |