Taxonomy field editors should work with published version

[tropcicstefan]

Describe the bug

In admin UI in content item editors with taxonomy field, user can select taxonomy term even though that version of taxonomy isn't published yet.
So if taxonomy is in draft should it be available to be picked?
If an answer to the previous question is yes, then what is the reason for taxonomy to be draftable and then this code in TaxonomyContentsAdminList is bugged.

To Reproduce

Create taxonomy add some terms, and publish taxonomy, then add additional term but don't publish the taxonomy.

Expected behavior

I see taxonomy as a backbone of the site so if something is in preparation, to be decided, changed whatever, it shouldn't be available throughout whole site.

[deanmarcussen]

Can you just change the taxonomy content type and remove draftable?

[tropcicstefan]

I could change it through UI, but then versioning is lost, because of the way AdminController works.
For my app I built custom driver so it's not like I need this change, but just thought there are discrepancies between field and admin list filter. And in logic if something is drafted vs published.

Although that line of thinking could solve #7054

In the end it's architectural decision

[sebastienros]

I am confused about the issue. @deanmarcussen seems to think it's about the admin filter (based on your link).
Can you explain what behavior your are seeing and are not expecting?

In admin UI in content item editors with taxonomy field, user can select taxonomy term even though that version of taxonomy isn't published yet.

That is not a bug to me, that was intentionally designed this way. And I don't see what issue there is with it, hence why I am asking you to describe the expected behavior.

[tropcicstefan]

Blog recipe
added food category to taxonomy

didn't click publish on taxonomy

go to blog post, there is food

look into taxonomy filter on content items list, there is no food

so the question is, is drafted taxonomy valid (can be used throughout the system) or not?
if yes then filters should have those terms, if not then field editor shoudn't show those terms.

[sebastienros]

filters should have those terms

yes

Then should we allow a published content item have a draft-only field? I think we can do too, but querying should take that into account and the behavior configurable in the queries (not returning a content item for instance on the front-end).

[github-actions]

It seems that this issue didn't really move for quite a while. Is this something you'd like to revisit any time soon or should we close? Please reply.

[github-actions]

Closing this issue because it didn't receive further feedback from the author for very long. If you think this is still relevant, feel free to reopen it with the requested details.