Contenttype in 2 taxonomies not showing ordernumber when "has_sortorder: true" comes second

[evertalbers]

I noticed that if a contenttype goes into 2 taxonomies and the second taxonomy is a
behaves_like: grouping
with a
has_sortorder: true
the sortorder number works OK behind the taxonomy tab in every single record but is not always shown in the contenttype overview page in the Bolt backend.

In a recent example (where projecttypes is the one with a sortorder, programlines is a category taxonomy) I noticed that changing
taxonomy: [ 'programlines', 'projecttypes' ]
into
taxonomy: [ 'projecttypes', 'programlines' ]
in contenttypes.yml solved this. So apparently, the taxonomy with sortorder should be mentioned as the first one.

If you see this as a bug, it should be solved in the code, if you regard it as a feature, it should be documented. :-)

[evertalbers]

This is the ordernumber that may or may not be shown, in case the written decription is not entirely clear. (And don't you love those huge 4K monitor screenshots?)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Maybe this issue has been fixed in a recent release, or perhaps it is not affecting a lot of people?
It will be closed if no further activity occurs, because we like to keep the issue queue concise and actual.
If you think this issue is still relevant, please let us know. Especially if you’d like to help resolve the issue, either by helping us pinpointing the cause of a bug, or in implementing a fix or new feature.

[evertalbers]

Reviving. This may still deserve someone's attention, I think.

[psanchezg]

Same problem here.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Maybe this issue has been fixed in a recent release, or perhaps it is not affecting a lot of people?
It will be closed if no further activity occurs, because we like to keep the issue queue concise and actual.
If you think this issue is still relevant, please let us know. Especially if you’d like to help resolve the issue, either by helping us pinpointing the cause of a bug, or in implementing a fix or new feature.

[bobdenotter]

Let's keep this around.. Can't promise I'll have time to fix it anytime soon, but it does look like a bug.