Redmine

Hi Oliver,

welcome to the forums and: Yes, you're on the right board :-)

Are location:plant and plant:project_number both 1:n oder are projects shared among plants or even locations?
Can projects be run jointly in different locations, say Geesthacht, Teltow and Berlin? What axactly do you need the herarchy for?

Look at RedmineProjectSettings, the sharing of issue categories follows the same principle as sharing of verions.
If you need the information for some kind of reporting, then you could perhaps use self-defined fields.

Don't hesitate to ask your other questions as well :-)
Regards
Jan

Hi Jan,

thank you for your reply.

In fact most of the projects are 1:n relations (95% i think).
<location> 1:n <plants> 1:n <projects> 1:3 <subproject for each department>

But sometimes we also duplicate a Project for an other plant eg.: a mobil vacuum pumping station
Up to now we have to remember witch parents-plant hold the documentation. (Of course there is a branch in the repository for the new plant.)
And of course it would be nice if there are a possibility to set a link in the project hierarchie.

Reading the sharing of issues again show me that this way should be a sharing of wohle projects, isn't it?

But the main question was how to build the hierarchy so a user see the projects ordered by eg. the location or by the plant-name.
Up to now it seemed for me that there ist only a flat structure of all projects he is working on with no chance of sorting them when he click on the project site of redmine.

Or is it possible that the user can filter/search in his involved project for self-defined fields?
So we can add two fields for each project, one for the location and one for the plant. And the user can filter his project view for a (eg.) location.

Thanks a lot,
Oliver

There's .../redmine/projects which lists all projects the user has access to.
The visual representation depends on the theme, in "Standard" it's like in the attached image. It's sorted by project name.
There's a (old) plugin called "projects tree view" touching this topic, but basically, this is a static list of projects the user is involved in. No sorting, filtering or anything else.

Up to now it seemed for me that there ist only a flat structure of all projects he is working on with no chance of sorting them when he click on the project site of redmine.

Indeed.

Or is it possible that the user can filter/search in his involved project for self-defined fields?
So we can add two fields for each project, one for the location and one for the plant. And the user can filter his project view for a (eg.) location.

No, that page is static, the user would have something like this:

+Berlin
+- Plant A
   +- Project A.a
   +- Project A.b
   +- Project A.c
+- Plant B
   +- Project B.d
   +- Project B.e
   +- Project B.f

Geesthacht
+- Plant C
...

What I don't understand: Why filter at all? You write

the user can filter his project view for a (eg.) location.

Imagine this is possible. Now, the user has activated a filter on, say, Berlin. Now all plants and projects belonging to "Berlin" are seen.
What does the user do now?
I'm trying to understand what you're trying to achieve, the better I understand your needs the better I can help you.

Hi Jan,

thank you for spending all the time try to understand my question.

No, that page is static, the user would have something like this:

Berlin
- Plant A
- Project A.a
- Project A.b
- Project A.c
- Plant B
- Project B.d
- Project B.e
+- Project B.f

Geesthacht
+- Plant C
...

There is my main question: Have i generate a project called "Berlin" and a subproject "Plant A" to generate this 1:n relation overview for the user?

The Problem with the flat structure in the project site of the user is:
As i wrote i'm working in a research center and the trouble ist that there are many changes (projects) on the instruments (plants) and we are only few people whos are working and planning for them.
Often it is necessary to take a look in the dokumentation of old projects because there are interfaces between them and the new project.
That is the reason why i think we couldn't close the projects in redmine for the engineer. But than his project site will only growing up.
(Here was the idea withe the additional fields for the location and the plant name and the possibility to filter all projects for a specially plant e.g.: Plant A.. This would be a virtuel hierarchy against the static one creating project for the location and for the plants.)

Up to now we saved all our project documentation in CVS repositories. And we start with a flat structure with an ID before the project name. But now we have to search a lot of time by hand to find the project in the ring field of TortoiseCVS or Cervisia (Linux).
So one of our three department decide to generate the hierarchie (location/plant/project/subProjectForEachDepartment).
We hope now to generate this new hierarchie in redmine and are not sure if we have create a project for a location.

Do you know som books explaining the first step building a usefull hierarchie with redmine.

I setup a virtual server with redmine and take them with me to my business trip the next three days.
There i hope i can try a lot creating a hierarchie under redmine.

Yours sincerely
Oliver

There is my main question: Have i generate a project called "Berlin" and a subproject "Plant A" to generate this 1:n relation overview for the user?

Yes

Often it is necessary to take a look in the dokumentation of old projects because there are interfaces between them and the new project.

Perhaps it would be an option to relocate (move) finished projects to be subprojects of a master-project "Archive"?

Do you know som books explaining the first step building a usefull hierarchie with redmine.

Well, there are actually very few books covering redmine, the latest being Mastering Redmine...