Re-Noticing @-mentioned users in a page

[Kim Trask]

Hi,

A large number of users in my company share a tabular weekly schedule that's hosted on a Confluence (Data Center) page. Not every user in this group is "on-schedule" for a given week. Scheduled users are @-mentioned in work-type rows that are meaningful to this usergroup (they don't use a database structure or Gantt report). They departed from saving weekly pages earlier this year and instead over-type the previous week's schedule. (if useful, I could have the reinstate weekly pages)

Sometimes the schedule changes after initial release and all on-schedule users need to be informed.

What I have read is that an @-mentioned individuals are only provided an email notice once per page. If a program lead "releases" the schedule by typing a page comment, is there a commend that would force an email notice to re-send to all @-mentions on the page (like @allMentionedUsers, or similar)? Can the same function propagate notice emails if the schedule is re-released?

It's desired to have a chronology of when releases are sent and that every @-mentioned user on a given page receives a common update.

I would rather not be driven toward emailing a security group the page link via Outlook to accomplish the same.

Thanks,

~Kim

[Barbara Szczesniak]

@Kim Trask I'm currently on Cloud, but trying to remember my server days from my last company.

Would it work to have all these people watch the page? Then, when publishing the updated page, the publisher could select Notify Watchers. 

I remember getting emails where I could see what information changed on the page. I'm not sure if this email feature has changed, but it would at least prompt all of the people to look at the page. I presume that you also want the people who are removed from the schedule to know, not just the ones you add with an @mention.

[Kim Trask]

I considered page watchers as a solution, and that might be where we land, it's one item on the buffet of options. What I don't like about page watchers is that the watcher must join as a watcher to the schedule page. It is a large group, to ensure everyone is updated, someone will need to be gatekeeper of the watchers. Unless we take the schedule out of its space and make a space for it. That's less likely to be received by the user group, though.

One solution on the table will be a Confiforms workflow. Because then I can guarantee who is notified at schedule release. And I can even control how the notification email appears.

Still, lightest weight seems to be email listserv with all the users, email to that group upon release(s). I would like a dynamic function that will force a notification only to the @-mentioned users on a page. That would be lightest weight and reduce spam.

Thanks for your consideration, Barbara.