Skip to content

Conversation

@fw-bot
Copy link
Contributor

@fw-bot fw-bot commented Mar 21, 2025

Description of the issue/feature this PR addresses:
The goals of the PR are multiple:

  • The thread names in the discuss app are not muted when "mute all conversations" is enabled or when the specific thread is muted.
  • The threads with no new messages are invisible when the parent thread is muted

Current behavior before PR:
see above

Desired behavior after PR is merged:
The thread opacity is set to 50 whenever the thread is muted (by any of the two ways)

task-4607160


I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: #202797
Forward-Port-Of: #200310

@robodoo
Copy link
Contributor

robodoo commented Mar 21, 2025

Pull request status dashboard

@fw-bot
Copy link
Contributor Author

fw-bot commented Mar 21, 2025

@KevGerard @alexkuhn cherrypicking of pull request #200310 failed.

stdout:

Auto-merging addons/mail/static/src/discuss/core/public_web/discuss_sidebar_categories.xml
CONFLICT (content): Merge conflict in addons/mail/static/src/discuss/core/public_web/discuss_sidebar_categories.xml
Auto-merging addons/mail/static/tests/discuss/core/public_web/sub_channels.test.js

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

@robodoo robodoo added forwardport This PR was created by @fw-bot conflict There was an error while creating this forward-port PR labels Mar 21, 2025
@C3POdoo C3POdoo added the RD research & development, internal work label Mar 21, 2025
@alexkuhn alexkuhn force-pushed the saas-18.2-18.0-fix-thread-names-muted-424534-fw branch from eb902c4 to c7dd774 Compare March 21, 2025 16:59
Before commit:
The thread names in the discuss app were not muted when "mute all
conversations" is enabled or when the specific thread is muted

After commit:
The thread opacity is set to 50 whenever the thread is muted (by any of
the two ways)

task-460716

X-original-commit: b667941
@alexkuhn alexkuhn force-pushed the saas-18.2-18.0-fix-thread-names-muted-424534-fw branch from c7dd774 to 89fb146 Compare March 21, 2025 17:04
@C3POdoo C3POdoo requested review from a team March 21, 2025 17:06
Copy link
Contributor

@alexkuhn alexkuhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

robodoo pushed a commit that referenced this pull request Mar 21, 2025
Before commit:
The thread names in the discuss app were not muted when "mute all
conversations" is enabled or when the specific thread is muted

After commit:
The thread opacity is set to 50 whenever the thread is muted (by any of
the two ways)

task-460716

closes #202947

X-original-commit: b667941
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
@robodoo robodoo closed this Mar 21, 2025
@alexkuhn alexkuhn deleted the saas-18.2-18.0-fix-thread-names-muted-424534-fw branch March 24, 2025 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflict There was an error while creating this forward-port PR forwardport This PR was created by @fw-bot RD research & development, internal work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants