Prevent confusion generated by the top Help link
|Target version:||Candidate for next major release|
People often post here probably thinking they're posting in their local Redmine instance; if theirs also use the default blue theme the confusion is indeed easy and understandable.
This might have unknown privacy consequences if they post some private information crawled by a search engine (say e.g. Gloogloo).
Help is also the only link in the top of the Redmine page to be an external link but is still displayed as others Home, Administration, etc., thus adding to the confusion.
So what would you think to simply add the already used external icon before the Help link to prevent this confusion starting from the next release?
Opening the page in a different window would be great too.
Any other ideas?
#5 Updated by Etienne Massip over 4 years ago
Jean-Philippe Lang wrote:
If privacy is a concern, we could improve the warning on top of the new issue page on redmine.org (eg. make it clear that it's the Redmine issue tracker and that submitted data will be made publicly available on the internet).
Sure this would be great and if the letters "ON THE INTERNET" are bold it would reduce the confusion when posting an issue but still don't you think that marking the link differently to make sure they actually immediately understand they left their local site would be useful?
I know this mean some dev that should then be reverted specifically on redmine.org but it should be worth it?
OTOH nobody never ask for this which is surprising so maybe the case is not as "bad" as I might think :|
#6 Updated by John Gordon about 3 years ago
I have had a quite a few users confused at ending up on Redmine.org and not being able to log in.
Suggest the default install could ensure that the top banner is not the Redmine blue.
Add the CSS plugin and change the top colour on your install to something else than Redmine blue.
This would be solved by adding the CSS plugin as part of core so this can be easily changed by the local admin.
This should not waste code time fixing....just add some great new functions that will avoid it happening.