[CONTTAGS-76] Default implementation of content tagging for Assets Created: 18/Jun/19 Updated: 23/Aug/22 |
|
| Status: | Open |
| Project: | Content Tags |
| Component/s: | None |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Team: |
| Description |
|
In M6.0 the Assets app has content tags enabled. I can see any existing tags in the browser view and the detail view. In M6.1-SNAPSHOT 2019-06-18 the Assets app does not show any tags, although when I view the assets in the JCR browser I see that they do have tags. The Assets app should have tags enabled as this is a standard use-case for tagging. Notes:
|
| Comments |
| Comment by Christopher Zimmermann [ 19/Jun/19 ] |
|
If DAM module adds the tag UI, what will happen on community edition where tags are not present/supported? |