-
Suggestion
-
Resolution: Unresolved
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
See Atlassian Answers Content By Label discussion.
OR logic between labels makes sense as long as you don't have any required labels, i.e. it will return pages that have at least one of the labels specified. However, once you add a required label (+label), the other non-required labels become optional and the results include pages with just the required label. The required label should be applied in addition to the other labels listed in the configuration.
Operator: OR (default)
Configuration: aa,bb
Results: Returns pages labeled with aa, bb, aa/bb
Configuration: aa,bb,+cc
Results: Returns pages labeled with aa/cc, bb/cc, aa/bb/cc, and cc (<-- this, pages with just cc, is the problem)
- is related to
-
- Closed
[CONFCLOUD-29796] Content by label logic is flawed when using a required label
I must point out that this issue should be reclassified to bug again. Because if we also review explicit label exclusion then concerned logic is not consistent at all.
If we assume that current implementation for required label (explicit addition) is wanted behavior (then desired functionality in this issue is really an improvement) then in that case explicit exclusion of label should work the same way, but it doesn't.
Operator: OR (default)
Configuration: aa,bb,-cc
and current implementation gives
Results: Returns pages labeled with aa, bb, aa/bb and these pages don't contain label cc.
but if current implementation for addition is desired behavior and exclusion should work the same way then implementation should gives
Results: Returns pages not labeled cc(includes pages labeled aa, bb, aa/bb) plus pages labeled aa/cc, bb/cc, aa/bb/cc (but it doesn't)
From these conclusions there is definitely a bug but depends where. In explicit addition or explicit exclusion ?.
Rostislav Simonik
added a comment - - edited I must point out that this issue should be reclassified to bug again. Because if we also review explicit label exclusion then concerned logic is not consistent at all.
If we assume that current implementation for required label (explicit addition) is wanted behavior (then desired functionality in this issue is really an improvement) then in that case explicit exclusion of label should work the same way, but it doesn't.
Operator: OR (default)
Configuration: aa,bb,-cc
and current implementation gives
Results: Returns pages labeled with aa, bb, aa/bb and these pages don't contain label cc.
but if current implementation for addition is desired behavior and exclusion should work the same way then implementation should gives
Results: Returns pages not labeled cc(includes pages labeled aa, bb, aa/bb) plus pages labeled aa/cc, bb/cc, aa/bb/cc (but it doesn't)
From these conclusions there is definitely a bug but depends where. In explicit addition or explicit exclusion ?.
Completely agree. I totally expected the default here to be AND not OR. I had a nice product page and i wanted to show release notes related to that product (one tag for product, one tag saying it's a release note) but to get all release notes for all products as well as every single page related to that product is completely useless.