Thanks Babynus, for that tip!
Yes, I corrected that global parameter, and now all resources can see the tasks from the Timekeeper (admin-type) project.
To conclude, this is a minor bug: [BUG]
The Administration projects should be exempted from this global parameter, because the tasks in it are always "dummy", and all resources in the organization would be entering time tickets repeatedly against the same tasks.
Thus these admin-type tasks (leave, training...) cannot have any responsible person for them, any start date, any handled status, etc to begin with.
The Administration projects should be exempted from this global parameter, because the tasks in it are always "dummy", and all resources in the organization would be entering time tickets repeatedly against the same tasks.
No, I don't agree at all.
It is not because they are Administrative that they don't have a workflow.
I have "Holidays 2018" that is in progress, in have created "Holidays 2019" but it is still "recorded". It will be "In progress" in september. So I can prepare next Admoin tasks...
Oh ok, I see what you mean: All these tasks won't be handled till the project is actually started off. Yes, that's right!
BTW I had raised BUG#2 on 1st June. I await your response to that.
Thanks in advance!
The screen has other issue also: Although the Project filter is set to DEMO-TSS, it actually shows an element from another project called TDA for ESL. [BUG#2]
Filter on project is not applied to Timesheet.
On this screen, you need to see all entered work, whatever the project selected.
The screen has other issue also: Although the Project filter is set to DEMO-TSS, it actually shows an element from another project called TDA for ESL. [BUG#2]
Filter on project is not applied to Timesheet.
On this screen, you need to see all entered work, whatever the project selected.
OK, but if the filter does not work for a particular screen, it should be automatically hidden.
In other words, show a control only if it has an effect on the display. Otherwise hide it.