Existing threads behaviour when threads are disabled

[MartinSchoeler]

Steps to reproduce:

1. Start a thread somewhere.
2. Disable threads
3. Open the created thread

Expected behavior:

In my opinion the thread should open, but it should be read only

Actual behavior:

A toast with the error "Not allowed" shows up and the thread sidebar loads indefinitely

Server Setup Information:

• Version of Rocket.Chat Server: 2.2.0-develop

[carpecodeum]

i want to work on this

[carpecodeum]

hey @MartinSchoeler i was thinking to remove the message box when threads are disabled. does that sound fine?

[abhishuraina]

I am working on it.

[subham103]

The current behavior is, if the thread is already open and we disable thread, we can see the messages on that thread plus can add replay on that thread, but those messages (after disabling the thread) comes with a grey color.

But if the thread is closed and we disable the thread, then it shows not allowed as mentioned above. Will try to work on this issue:)

[subham103]

The thread's side-bar can be easily shown by removing the check. The big question is Should we give the option to write on the thread after it is disabled? I think it should be read-only as mentioned by MartinSchoeler, and we should remove the input box inside the side-bar if the threads are disabled.

@MartinSchoeler , guide us to the intended behavior

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.