- Posts: 13
- Thank you received: 0
It's not a bug, it's a feature.Possible Bug 1:
In "Work Time" section of "Global Parameters", even if you change "Daily Work Hours", "number of hours per day" does not change and unfortunately its field is disabled. For instance, our company's work hours was 8,5 hours in a day, now it has been increased to 9 hours, but i cannot reflect this situation into Projeqtor.
It's not a bug, it's a feature.Possible Bug 2:
When "Pools of Resources" are used in activities, and when in their "Assigment Properties" "unique resource" is selected, activity costs are not calculated in no way.
This good be a good option, the have dedicated "Assignement" screen. This would require accurate filters to find the correct list you need.Suggestion 1:
There is no seperate assigments section of a project, other than activity properties window. Therefore it is inpossible to export project assigments into a csv file. For that reason, resource fluctiations cannot dynamically be reflected into the program. The only choice is by editing resources by one by inside the program, but it is extremely slow and painful. If a seperated assigments window is generated for a project, many things get easier.
I really don't thing a CSV file will give better visibility.Suggestion 2:
There is no seperate section which display predecessors/successors of a project, so, when project activities grow in number, it is also painful to produce predecessor/successor links. And, for this reason, it is also impossible to export predecessors/successors of a project into a csv file, in that case, the links can easily be constructed in Excel for instance, by depending activity id's.
At least the search tool existsSuggestion 3:
In Projeqtor, there is a search tool that is used for several purposes, linking, connecting activities, other objects etc. However again, when project activity number grows, this search tool sucks. Because, when activated, it first tries to list activities, and you wait... But, you want to link to a milestone for example. Intead of obtaining complete activity list from the server, it might be better to send query to the server first, then display the query result. This search tool, at the beginning, should do nothing.By behaving like this, the user will have a possibility to choose what kind of search he/she is going to make. I think this way will produce quicker results.
If you wait long, possibly your server is over loaded. Maybe a technical analyses to improve its performance may help. Also, user project selector filter will help limit number of activities so that lsit is not so long to display.Because, when activated, it first tries to list activities, and you wait
I don't understand that point. Of course query is se,nd to the server the result is displayed...Intead of obtaining complete activity list from the server, it might be better to send query to the server first, then display the query result.
This could be an option (keep list empty until selection of target list). But ProjeQTOr tries to ease use by selecting target that seem to be the most frequently use (the most efficient).This search tool, at the beginning, should do nothing.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
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.
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.