Unit History invitations for Branch-specific callings

[BrianEdwards]

This is a question for anyone in a Branch who could check. When we go to the new Unit History "Manage => Story Manager => Invites", there's the standard "Add Recipient" button, which when clicked brings up the list of potential authors. What we see (and have always seen since the tool went online), is that it defaults to what I'll call "Ward-specific callings", and "Branch-specific callings" are not listed.

So for example, the "Bishopric" is the first section, and each entry says "Bishop - Not Assigned", "First Counselor - Not Assigned", etc. Of course we don't have a Bishop, or a Bishopric First Counselor, we have a Branch President, and Branch President First Counselor, etc.

Also, at the bottom it says "Ward Mission Leader - Not Assigned", whereas we do have a "Branch Mission Leader" that doesn't show up in the list. All the other callings are filled out correctly (EQ/Primary/RS/SS/YM/YW).

I'm wondering if this is a general bug in the system that all Branches see, or if for some reason it just is affecting us. If somebody could check what they see (or let me know if they're using this successfully in their Branch), we'd love that.

[jstamps]

This might be one of those situations where 'ward' is just substituted for 'branch'.
Everyone in our ward was "Not assigned" for a week or two last month, but then it was correct again. (https://tech.churchofjesuschrist.org/fo ... 75#p247375 from Jan 21.) I had sent feedback through the page, but i dont know if that's what got it corrected. I wondered if it needed to repopulated after some system change.

[BrianEdwards]

We have seen the same thing since the Unit History tool first became available for us, and it's still the same as what I described above. We have been using the tool somewhat regularly, and every time I check there's no difference in what's shown. If other Branches are seeing the Branch Presidency listed correctly, and the Branch Mission Leader listed correctly, then it's somehow specific to our unit.

[ctcoombs@hotmail.com]

I am the clerk in a Branch and having the same problem. It seems the system was set up for a ward.

[BrianEdwards]

I am the clerk in a Branch and having the same problem. It seems the system was set up for a ward.

Besides what you posted in the other thread (which is that you already tried submitting Feedback), I think the only other possible option is to speak with your Stake History Specialist, who may have access in their stewardship, to somebody at the Area level who is over history efforts. I've done that myself, no luck yet.

Other than that, there's always a possibility that our Forum discussion might catch the eye of a Church employee who can bring this to somebody's attention behind-the-scenes. Not likely, but I'm an eternal optimist!

[ctcoombs@hotmail.com]

I contacted the Stake History Specialist and he couldn't find a way to get the Branch Presidency included. Hoping someone who know how to fix this will give us some ideas!!

[cmanley51]

I am the History Specialist in a Branch.
How can we add the Branch Presidency and Branch Mission Leader names to the author and approver lists? Currently the list shows those positions as "Unassigned". thank you.

[BrianEdwards]

I am the History Specialist in a Branch.
How can we add the Branch Presidency and Branch Mission Leader names to the author and approver lists? Currently the list shows those positions as "Unassigned". thank you.

Please see the the post two before yours. For reference, this Forum is comprised mainly of regular members like yourself, and primarily serves as user-to-user discussion. There appears to be nothing we can do locally to fix the issue being discussed, it seems to be something the Church must do programmatically on their end of things.

Note that the Branch President and the Branch Mission Leader are still able to create and submit stories, they currently just cannot be invited to do so using the unit history functionality.

[jstamps]

It's probably something that will take some additional coding with additional links to a database.
You should definitely use the Feedback link on the page to report the problem. It should be on the right side toward the bottom.