Must always list inherited item
Must always have inherited or aliased item listed in every row.
1. It needs to be there for comparison.
2. It is the only way to delete an item (eg when only some of a logical group is present, and the values need to be removed).
3. That allows people to vote for "same as parent" as opposed to "explicit value".
That is, there must always be an inherited value (#5bc0de in every row OR an aliased (#ddf value in every row.
Attached are examples of failures to do this.
Trac Comment 12 by —2018-09-27T18:19:48.384Z
I suggest that we close this ticket, since the specific bugs illustrated in the original links for this ticket have been fixed (on SmokeTest). I've opened a new ticket  concerning the third screenshot ("where we can't delete an item").
There are still many other cases in which a row contains no inherited item. Some rows have no items at all. When is that an error, and when is it just a correct description of the actual situation? For example, recent discussion of ticket  suggests that it's not an error when a "synthetic" (a.k.a. "extra"?) row has zero items (such as <http://cldr-smoke.unicode.org/smoketest/v#/nl/SAmerica/4abcd3554b48611b>).
There are many other open tickets concerning inheritance, such as  and , and I'd like to follow up on the question of when an inherited item is required in the context of those tickets.
Trac Comment 9 by —2018-09-26T19:33:58.490Z
Per today's meeting I've assigned this to myself. The problems shown in the first two screenshots have been fixed, probably by the changes for ticket . These now show inherited values on Smoketest:
The third screenshot illustrates a different bug, for which I'm going to open a new ticket.
Trac Comment 8 by —2018-07-22T17:47:03.369Z
This is possibly a duplicate of , for which a fix  is ready for pushing to production.
Trac Comment 6 by —2018-02-19T14:08:33.394Z
Inheritance may breaks down in some areas. In general, the UI/backend for inheritance needs a end-to-end review.
Trac Comment 1 by —2017-08-21T13:47:00.269Z
Added an attachment showing a case where people (even TC) can't delete an item in the ST.