Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visibility of report status changes' motivations #4201

Open
evariitta opened this issue Sep 26, 2024 · 5 comments
Open

Visibility of report status changes' motivations #4201

evariitta opened this issue Sep 26, 2024 · 5 comments

Comments

@evariitta
Copy link

Proposal

We have an issue with transparency of status change motivations.

Recipients were unaware that the motivations they wrote when closing reports would later be visible to whistleblowers. It would be problematic to let whistleblowers see texts that recipients believed were private.

Motivation and context

We wouldn't have this issue if previously written texts didn’t become retroactively visible after the version 5 update. Would it be possible to work around this somehow?

@evilaliv3
Copy link
Member

Thank you @evariitta for raising this concern. that is is very valid.

Unfortunately, the problem lies in a contribution that we received to support a national authority that has in fact this usability issue.

The current implementation considers that the motivation should be transparently shown to whistleblowers following the same principles of any information that the platform tracks and this choice is based on the same principles of transparency and accountability of the entire project.

Unfortunately even if discussing to have found a solution i dont think one exists. I do not see an easy solution since some users may have thought it was public and others private so we can simply flip the visibility.

I suggest we could just document a query to remove the motivation of the system, so that organizations that may have incorrectly thought this information was private could remove the motivation of all the existing reports or an existing set of reports given that date.

Lets see what other of the most relevant users of the system thing to find a strategy to mitigate the issue that you are describing.

\cc @larrykind @elbill @giorgiofraschini @JaviAlama @msmannan00 @danielvaknine

@JaviAlama
Copy link

In our case we are not affected by this problem. Although we initially defined several statuses, we finally used the basic ones of New, Open and Closed. We incorporate other intermediate cases such as ‘Pending Acknowledgement of Receipt’, ‘in Processing’, ‘under Analysis’, etc...

The management of the complaint and the evolution of its processing is managed entirely through the Electronic File Manager. We use the mailbox to communicate with the complainant and we do not motivate the change of status, except at the closing when we incorporate the Resolution of Conclusion of the file.

@evariitta
Copy link
Author

Thank you.
A query would be helpful for us.

@danielvaknine
Copy link

After testing this feature out we agree that it is too unclear and unexplained to the user that the motivation becomes visible to the whistleblower.

We therefore suggest to either

  1. Not show the motivation to the whistleblower but only to the recipient(s)
  2. Clarify to the recipient that the motivation will be shown to the whistleblower

We suggest option 1 until enough languages have been translated to have an effective option 2.

@giorgiofraschini
Copy link

i quite agree with @danielvaknine on this. We should make it easier for the recipient to understand that this motivation will be shown to the whistleblower.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants