SR Ward Clerk wrote:Actually, counting my issue with adding a person as a leader in a quorum of a different priesthood office, along with the other person that reported it, makes two. I haven't had a reason to try to do it since early last year, and I tried three times then. It may have been fixed in versions that were released after that time. Also, as I'm sure you know, there are many clerks that don't even use this Web site. I've never heard anyone in my stake mention it.As far as the home teaching districts issue is concerned, no one in my ward has tried to edit the assignments yet. My EQ president came to the office tonight to enter and view home teaching visits while I was updating the callings board in the bishop's office. He didn't have any problems with the mixed elder/HP companionships being cleared out, but he was not in the assignments screen, so it probably wasn't an accurate test.
This thread is discussing changes caused by the MLS 3.0 upgrade, so any issue that predates the conversion to MLS 3.0 would belong in a different thread. But we have multiple reports that there is no problem in current MLS (2.9.4 or 3.0) with adding a person with another priesthood office to the leadership of a quorum, as long as you add them to the quorum organization first. I'd recommend you try that procedure now. If you have problems, please report it in a new thread, since it is not specific to MLS 3.0.
My comment about wanting additional verification referred specifically to the issue reported by preston.baxter where existing HT assignments made to Elders in the HP organization (or vice versa) were disappearing when you simply view such assignments. That's the issue I was counting results for, and at this point, there is still only one report of that problem (and two reports that such a problem does not occur, as well as a post stating that such an issue has not been reported to Local Unit Support). I think it's safe to conclude that that particular issue is not a general problem with MLS 3.0; either the report is not accurate, or the issue is specific to one installation of MLS 3.0.