# Notification sent wrong for shared draft with changed owner
**URL:** https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301
**Category:** Bug
**Created:** [December 29, 2019, 1:47pm UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301 "2019-12-29T13:47:05Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Anatolia](https://meta.discourse.org/u/Anatolia)
#### Post date: [December 29, 2019, 1:47pm UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/1 "2019-12-29T13:47:05Z")
I just created a draft and in order to change its ownership to our official account I’ve posted into a restricted category. Then changed ownership and moved to a public category but notification sent have my name on it.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [December 30, 2019, 12:16am UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/2 "2019-12-30T00:16:28Z")
That is probably cause your account edited it. What is the exact repro of the issue and what is your expected behavior?
---
### Author:  [@Anatolia](https://meta.discourse.org/u/Anatolia)
#### Post date: [December 30, 2019, 12:49am UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/3 "2019-12-30T00:49:08Z")
I’ve edited its content and ownership before shared publicly. Then I edited the category to move new category. I thought it would sent notification with the name of latest owner of the topic. This was what I expected.
---
### Author:  [@Flashio](https://meta.discourse.org/u/Flashio)
#### Post date: [December 30, 2019, 11:41pm UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/4 "2019-12-30T23:41:35Z")
> [@sam](#):
>
> That is probably cause your account edited it. What is the exact repro of the issue and what is your expected behavior?
This bug was also posted by me in different exposition.
**The point is:** when topic creator changes something in the topic (category, tag, etc.) - ALL users that “watching” this category or this topic - they all will receive a notification. After user will press on notification - he will be redirected to the first post of that topic.
This causes a problem when you using “telegram notification plugin”. All users will receive first message of the topic again after something changed in it.
I’m begging you to fix that.
> [@All users with "watching" subscription on category receiving notification when topic starter changes a topic's tag](https://meta.discourse.org/t/all-users-with-watching-subscription-on-category-receiving-notification-when-topic-starter-changes-a-topics-tag/135114):
>
> To activate the bug topic starter must create topic with tags, after that he must reply to that thread and topic starter’s message must be last in the topic. After that if topic starter will change the tag, then discourse will send notification related to the first topic’s message. Summary: Topic Starter must create a topic Topic Starter must reply to this topic and his reply must be the last Topic Starter must change the topic’s tag. And now every time he change the topic’s tag everyone who …
---
### Author:  [@Anatolia](https://meta.discourse.org/u/Anatolia)
#### Post date: [December 31, 2019, 2:42pm UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/5 "2019-12-31T14:42:16Z")
This is happened again. If I create a shared draft then change its owner and share it into a public category, it’s sending a notification with the name of creator of post instead of latest owner.
Also interestingly I’ve got the notification correct but other users reported they receive different notification.
 
---
### Author:  [@Flashio](https://meta.discourse.org/u/Flashio)
#### Post date: [January 16, 2020, 2:53pm UTC](https://meta.discourse.org/t/notification-sent-wrong-for-shared-draft-with-changed-owner/137301/6 "2020-01-16T14:53:05Z")
Was it fixed or will it be fixed in near future?