On reserve ordinance page the parents are listed female on top vs traditional landscape pedigree of

LegacyUser

Allan Hale said: Family Tree has established the non traditional landscape pedigree with the male on top and it has been working for nearly 15 years. Now recently on the reserve ordinances page in the SP the female is on top. You set the standard why change it.

LegacyUser

Jeff Wiseman said: Allan,

I'm not a FS employee, so I'm definitely no spokesperson here :-)

However, the issue you bring up seems to be a variant of some bugs that FS was dealing with just a couple of weeks ago. What you are describing may be a bug that needs fix'n.

If you could provide a PID number of a record where this behavior is visible (or even a screen shot), it could go a long ways in assisting the engineers in fixing it.

LegacyUser

Jeff Wiseman said: Now sure about the "reserve ordinances" page, but if you were referring to the Ordinances tab on an individual record, I think I see what you are talking about:



Note that there appear ok in the pedigree:



macOS Sierra 10.12.6, Safari 12.1.2

LegacyUser

Jeff_Luke said: Here's another example of nonsensical ordering of male and female. Sometimes the male name is on top, other times it is the female.

LegacyUser

Jeff Wiseman said: That looks a little closer to what I think Allan was talking about.

Nicely scrambled :-)

LegacyUser

Allan Hale said: Ok I will create a case for it. I remember the problem now. Guess it never got fixed.

LegacyUser

Tom Huber said: Yeah, it is definitely a bug. Since every message is read by a FamilySearch person, they will also likely pass on the problem to be addressed by the team(s).

LegacyUser

Lyle Toronto said: This is a relationship position problem. Because FS went to a gender agnostic couple model (spouse1, spouse2 and parent1, parent2) the couples can be stored in any order. There is a distinct order for the spouse relationship and a distinct order for the parent child relationship. These are usually the same, but they can be different.
It seems that SS is tide to the Couple Relationship and SP is tide to the Parent Child Relationship.
In this case the Parent Child relationship seems to be flopped while the Couple relationship is in the traditional order.
If you look at the Relationship popup for the parent child relationship (the same place you add adoptive, step etc) there should be a "switch position" link at the very bottom. This will put the couple relationship in traditional order.

LegacyUser

Jeff Wiseman said: That's not the issue. Bugs associated with the gender agnostic display in the pedigree were fixed a ways back but this was missed. Otherwise, in my example above with Johann Grumping and Mary Frey, why are they in one (i.e., the correct) order in the pedigree and reversed on the ordinances tab?

In any event, the instructions are moot because with a traditional couple relationship that "switch positions" button is not made available:





The display in both the temple lists and the ordinance tabs are broken and likely need the same type of fix that was applied to the pedigree charts several weeks back.

LegacyUser

Lyle Toronto said: Yep, I was wrong. Looks like a bug.