View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Organization and parent Organization - Page 4 - ProjeQtOr
 

Organization and parent Organization

More
17 Apr 2017 19:02 - 17 Apr 2017 19:04 #19 by babynus
In OrganizationMain->updateBudgetElementSynthesis(), following code in not compliant with PostgreSql
$whereClause .= '(
                            (idle=1 and
                                (
                                    (isnull(realStartDate) and isnull(realEndDate)) or
                                    (isnull(realStartDate) and year(realEndDate)=YYYY) OR
                                    (isnull(realEndDate)) OR
                                    (year(realStartDate)=YYYY or year(realEndDate)=YYYY)
                                )
                            ) or
                            (idle=0 and
                                (
                                    (isnull(validatedStartDate) and isnull(validatedEndDate)) or
                                    (isnull(validatedStartDate) and year(validatedEndDate)=YYYY) OR
                                    (isnull(validatedEndDate)) OR
                                    (year(validatedStartDate)=YYYY or year(validatedEndDate)=YYYY)
                                )
                            )
                         )';
as isnull is not available on PostgreSql

Exact replacement that works is
$whereClause .= "(
                            (idle=1 and
                                (
                                    (coalesce(realStartDate,'null')='null' and coalesce(realEndDate,'null')='null') or
                                    (coalesce(realStartDate,'null')='null' and year(realEndDate)=YYYY) OR
                                    (coalesce(realEndDate,'null')='null') OR
                                    (year(realStartDate)=YYYY or year(realEndDate)=YYYY)
                                )
                            ) or
                            (idle=0 and
                                (
                                    (coalesce(validatedStartDate,'null')='null' and coalesce(validatedEndDate,'null')='null') or
                                    (coalesce(validatedStartDate,'null')='null' and year(validatedEndDate)=YYYY) OR
                                    (coalesce(validatedEndDate,'null')='null') OR
                                    (year(validatedStartDate)=YYYY or year(validatedEndDate)=YYYY)
                                )
                            )
                         )";

But this selection criteria does not please me, as it will select same Project on several budget years.

I propose to replace it with :
$whereClause .= "( year(coalesce(validatedStartDate,realStartDate,plannedStartDate,initialStartDate))=$periodValue )";
So project is counted on year of first not null value for
1) validatedStartDate if set
2) realStartDate if set
3) plannedStartDate if set
4) initialStartDate if set

Babynus
Administrator of ProjeQtOr web site
Last edit: 17 Apr 2017 19:04 by babynus.

Please Log in or Create an account to join the conversation.

More
07 Jun 2017 19:59 #20 by tabary
Hello,

I'm back.

Projeqtor was chosen by a major distributor in the South West region of France to manage all the projects related to the redesign in its information system and the management of the DSI projects on the existing one.
The functionalities used will be:
  • Projects and planning
  • Imputation
  • Organization (the budgetary aspect is not essential at the moment)
  • Requirements and tests
  • Ticket (for the management of the anomalies linked to the test sessions)
  • Available
  • Product
This is a context in which both the volumetric
  • projects,
  • activities,
  • organizations
and the associated hierarchy levels
 are important.

In this context, I realized that the performances were not at the rendezvous, especially at the level of imputations (TimeOut regular).
In fact, the implementation I have done in the consolidated calculation of budgetElement is far from optimal.

While waiting to rework on the subject, I propose the following alternative:
Add a parameter ('useOrganizationBudgetElement') whose values ​​are 'YES / NO' in the 'sectionOrganization' section.
If this parameter is set to 'YES', then same operation as before.
Otherwise, the budgetElement is no longer used and the detail screen of 'Organizations' no longer shows the data corresponding to the BugdetElement.
The project summary that is presented corresponds to the 'work', 'cost', 'expense' of the organizations' projects and their sub-organization, calculated (and not stored) data at each display of an organization.
This slows down the display but no longer disturbs the time recording.

The patches for the version '6.2' and '6.3', as well as the lang.xls, are delivered as attachments.

Hopefully this solution will suit you.

Best regards
Attachments:

Please Log in or Create an account to join the conversation.

More
11 Jun 2017 17:38 #21 by babynus
Your patch for V6.3 has been integrated.

NB : luckily, performance issues will occur only if organization is set on projects...

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.048 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.