Shared drafts are not Watched

It appears that when a shared draft is finally published after team edits, it is not considered a new topic.

No emails are sent out to members who are watching first post for the category.

I believe it should trigger emails when the publish happens.

Thoughts please.

1 Like

Tagging it as a bug now. Thanks.

Watching does not also happen when a new topic is created by splitting messages from an existing topic.

2 Likes

Sorry @Chandra, I haven’t had a chance to test this one out yet, but I don’t want you to think I’ve overlooked it. :slight_smile:

1 Like

Many thanks @JammyDodger
Most appreciate your update.

1 Like

Just to check before I dive in - is this using the shared edits plugin, or the shared drafts admin setting?

1 Like

The shared drafts admin setting:

Edit: I realized I used shared-edits tag, removed it now but don’t see one for shared-drafts.

1 Like

I don’t think I can replicate this?

My step-by-step:

  • Set shared drafts category and shared drafts min trust level both to staff
  • Set email time window mins to 1 (optional :slight_smile:)
  • Set test user A as Watching First Post for #general category
  • Create topic as ‘Shared Draft’, destination category #general
  • Use another test staff user to make edits
  • Publish draft

  • Topic is published to the correct category
  • Test user A receives notification about new topic
  • Test user A also receives email about the above notification

It generates notifications, though the emails would be controlled by each user’s Preferences, as well as if they’ve seen the forum within the email time window.

Did your workflow change the saved topic’s category from staff to a watched category at publish?

I have all members set to watch first post of destination category but no emails were generated.

I will be publishing a shared draft in a day or two and will trace it stepwise to review.

It did indeed. :+1: There’s also a bit more info on the feature in Shared Drafts: Allow staff to collaborate on posts before publishing if you need an overview.

I’ll slide this over into #support for now, but if you can replicate your issue we can always move it back again. :slight_smile: :+1:

2 Likes

Hello @JammyDodger
Not to “bug” you but wanted to let you know I have PMed you some screenshots I captured recreating the issue. Please review at your convenience, thank you.

1 Like

Having a quick look over your PM, it seems like at least one email was sent out as ‘Watching First Post’ for that shared draft, which suggests that it’s working.

In your notes, you refer to setting that category notification as a default for your users, but are you sure the default has been applied correctly? If you have the data-explorer installed, you could run a query to check your users’ category notification level for that category to make sure that they’re set as you expect:

(‘4’ is the code for ‘Watching First Post’, ‘3’ for ‘Watching’)

-- [params]
-- int :category_id

SELECT cu.user_id,
       cu.notification_level
FROM category_users cu
WHERE category_id = :category_id
ORDER BY cu.notification_level DESC
1 Like

Yes, worked only for 1 email of ~8000. Not sure what was special about this id :thinking:

I don’t have data-explorer installed but can try at next build.

Here are additional thoughts on what I think is the issue:

  1. Email sending to all works correctly in the same category for new direct (non shared-draft) topics. I will try to capture screenshots for that as well. So, the watch for all on the category should be good.

  2. I also noted notification emails are sent out to Staff email ids right at the first save. I believe this means the topic is triggering off the notification process right at first save and not after completion of multiple staff edits and actual ‘publish’. At the point of first save, the topic is in staff category and hence only staff members get notified.

  3. If shared drafts category is set to a non-staff category, I suspect this may email out incomplete posts to all watching members of the shared drafts category instead of the destination category.

1 Like