A few months ago, a team of developers at Blue Inc identified a new issue during testing and created a public channel called #bug-cricket to communicate about the issue. After some casual conversation back and forth in the channel, the team discovered that a problem with the old architecture caused this bug. They may need to reference the history in the future. Of note, there has not been any new activity in #bug-cricket for months, and the bug case has been closed. What should the team do with #bug-cricket?
A. Convert the channel to private, and then archive it; members of the channel will retain access to the files.
B. Remove all members from the channel, and then archive it; this way, members can find messages via search but will not be able to browse the channel history itself.
C. Delete the channel; messages from a deleted channel are still available via search.
D. Archive the public channel; anyone can still browse the conversation history in Slack, and messages will appear in search results.
Answer:D
A few months ago, a team of developers at Blue Inc identified a new issue during testing and created a public channel called #bug-cricket to communicate about the issue. After some casual conversation back and forth in the channel, the team discovered that a problem with the old architecture caused this bug. They may need to reference the history in the future. Of note, there has not been any new activity in #bug-cricket for months, and the bug case has been closed. What should the team do with #bug-cricket?
A. Convert the channel to private, and then archive it; members of the channel will retain access to the files. B. Remove all members from the channel, and then archive it; this way, members can find messages via search but will not be able to browse the channel history itself. C. Delete the channel; messages from a deleted channel are still available via search. D. Archive the public channel; anyone can still browse the conversation history in Slack, and messages will appear in search results.