-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? 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)
- relates to
-
- Gathering Interest
[CONFSERVER-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 ?.
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management