# 投稿時の通知レベル調整に関するタイムリーなユーザーフィードバック
**URL:** https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913
**Category:** UX
**Created:** [2018 年 2 月 6 日午後 2:55 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913 "2018-02-06T14:55:03Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [2018 年 2 月 6 日午後 2:55 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/1 "2018-02-06T14:55:03Z")
I know we currently have a user preference for which notification level to set topics to when posting:
But I just saw the “Subscribe me to updates” checkbox when commenting on a card in trello I’m not following:
Might be an idea worth stealing (in addition to the user preference for the default).
Why?
- It is more discoverable (not everyone knows to dig around in their preferences).
- It’s more clear what the effect of my action is when it’s coupled to the action
- It allows people to choose on a case-by-case basis
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018 年 2 月 6 日午後 11:09 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/2 "2018-02-06T23:09:56Z")
Seems quite redundant since the notification control is already there at the bottom of the topic, and does the exact same thing:
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [2018 年 2 月 7 日午前 9:26 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/3 "2018-02-07T09:26:26Z")
I like the idea of making this more obvious! 🙂
A (possibly stupid) alternative that’s less intrusive would be to flash the notification control after posting if the post caused a change there, just as we flash the actual post to guide the user’s eyes 🤔
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2018 年 2 月 7 日午前 9:37 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/4 "2018-02-07T09:37:29Z")
I like the idea of a subtle CSS transition but think it would be tricky to tie it to when it’s in view.
---
### Author:  [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [2018 年 2 月 7 日午後 12:05 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/5 "2018-02-07T12:05:51Z")
Trying out this customization to reduce the noise down there and see if it helps people see more clearly what’s going on with topic level notifications (It also has some nice symmetry with the buttons under the progress bar):
CSS:
```plaintext
#topic-footer-buttons .topic-footer-main-buttons {
float: left;
}
#topic-footer-buttons .topic-notifications-button {
float: left;
margin: 0;
}
#topic-footer-buttons .bookmark {
display: none;
}
#topic-footer-buttons .share {
display: none;
}
#topic-footer-buttons .flag-topic {
display: none;
}
#topic-footer-buttons .invite-topic {
display: none;
}
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 2 月 13 日午前 6:46 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/6 "2018-02-13T06:46:07Z")
Another atomic 💣 solution here is the user setting
> When I post in a topic, set that topic to: Watching
You could backfill it on for all your users, then force them to learn about the setting and how to watch topics individually. I can see that in email heavy orgs default of watching after posting making more sense.
---
### Author:  [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [2018 年 2 月 13 日午前 7:31 UTC](https://meta.discourse.org/t/just-in-time-user-feedback-for-notification-level-adjustment-when-posting/79913/7 "2018-02-13T07:31:39Z")
I have considered doing that. Could be worth trying out.
I still think the original request here has merit, but falls into a class of suggestion that isn’t exactly aligned with “complaint driven development,” since there is no strong complaint here, just an idea for an improvement to the user experience.