Redmine

+1 For now, we're using wiki of one project as global wiki, and I added link to whis Wiki to main top menu, with text "Wiki", but it's just a workaround hack ;)

+1 as I'm having to create some temporary hacks in order to present company wide information, like programming guidelines, vacation policies, etc. on the Home page. It would be great to have the ability for any module to be "site wide", including ability for existing permission settings, etc. these modules have.

+1

+1

+1

+1

+1

+1

+1
Would be great. That way, info that is meant to be company-wide could be published easily, without a need for workarounds.

+1 from me

+1

+1

+1
Would be great.

+1000 it would be really great, because a lot of companies hasbig amount projects which are similary... and it so stupid idea to have a lot of independent wiki... Also it good idea to have global file storage, global documents and global forum. I created for that separate project, but it not so good idea because it's not pure project, and it hard to find for people within big amount of real projects in project list... So please make this functionality, users really need it.

+1.3 :)

we're still using menu hack which point's to one project's wiki... no nice solution

Maxim: closing the duplicate won't close the original. But closing the original will close the duplicate.

Maxim Krušina wrote:

ssry, I din't know that linked issue will close both original and duplicate ;(

/me ranting out loud while being a bit corny {

He should know better... He should have been known to the automatic-duplicate-closure behaviour of Redmine since it was explained in-depth by J-PL in this forum-thread started by .... Himself...

}

:-)

JPL> Ach so, thnx! ;)
Mischa> There should be no "He should know better" in good app, all must be self-explaining. I just read again forum you sugested, but I think it should be much moe clear how the mechanismus work. All we are heavy Redmine users and even it's a bit confusing now, so some fine-tuning will help!
I bet there will be lot of other users a bit frustrated about this.

In other words: functionality is just OK, but it should be somehow better communicated and self-explaning...

+1

+1 It would be very helpful for me too.

I would implement this using the newly available unlimited project nesting, and thinking this global wiki as being "the wiki of the root project". Then we can discuss common trees behaviour like inheritance and accumulation. For example, "wiki inheritance" would allow a child project to reference a wikipage of a parent project using only the name of the page, i.e without mentioning the project name. Dynamic resolution would look parents project until it finds the page. I guess this is pretty much what you want for a global wiki

Paul Rivier wrote:

I would implement this using the newly available unlimited project nesting, ...

It is a good idea!

+1

Without this feature we will need to setup a completely seperate Wiki to hold general company information.

+1

+1 please

+1

+1

+1

+1

any news?

+1

+1 Good idea! The text could be 'Global Wiki'.

+ 1. We have several projects which all should have a common Wiki.

+1

+1. But as Feature #6027 mentions a global forum is just as important.

+1

We currently use a "General" project, but global wiki/news/forum would be more elegant.

Any news? <aol>me too</aol>

+1

+1. This is VERY VERY important. Please have it.

Add related - #1982

+1

+1.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1 (is anyone actually counting them?)

+1

+1

Hi Mizuki, thank you very much for your effort,

I will try it the next weeks but I have to understand the patch first,
which will take a bit cause I am new to Redmine.

Timo Schüring wrote:

Hi Mizuki, thank you very much for your effort,

I will try it the next weeks but I have to understand the patch first,
which will take a bit cause I am new to Redmine.

Thank you.

Conflict occurred when patching the latest Redmine trunk (r20825).
I will attach the fixed patch.
These patches are developed to be applied to Redmine under development (trunk, r20825) , so it may not be applicable to released Redmine such as Redmine 4.1.

Thank you again, Mizuki-san,

we use Redmine so far on our Synology NAS with an old version based on
a Docker package. So I guess I have to adapt the patch anyway.
And/Or I have to learn how to get the development patch running.

Environment:
Redmine version 3.3.10.stable
Ruby version 2.3.8-p459 (2018-10-18) [x86_64-linux-gnu]
Rails version 4.2.11.1
Environment production
Database adapter Mysql2

Thank you, Mizuki-san,

I managed to do some trivial changes to make it compilable on Redmine 4.1.1 and 4.1.2: https://gist.github.com/keineahnung2345/4f5eee59079128645cad8aa88016fa77/140e02176ad78bf45ab67dbb8de14c0487cf878f.

But later I found that there are permission problems or redirection path problems on some buttons(new button not showing, internal server error after editing, internal server error after deleting, rename button not working). So I made some changes to make them work as expected: https://gist.github.com/keineahnung2345/4f5eee59079128645cad8aa88016fa77/240d94bce8017f3e52cfce6f9101f39685c91888.

Could you please check the revised code and check if those problems also happen on truck r20825? Thanks.

Updated patch for redmine 5.0.5: https://gist.github.com/keineahnung2345/5431ffbde8f62698533c3ad5d9ffb840