Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

"Work not assigned"...
 
Notifications
Clear all

"Work not assigned" in Timesheet when dispatching work on new ticket

4 Posts
3 Users
0 Reactions
792 Views
(@john-k)
Posts: 2
New Member
Topic starter
 
[#9795]

Hello,
I have an issue with the Timesheet screen. Here is what I do:

Prerequisite: A new Activity has been newly created by my Project leader.

0. Log in as a Project member.
1. Initiate a new Ticket: fill the title, set me as responsible and link it the new activity as planning activity. Then save to create the ticket.
2. In section 'Treatment', click "Dispatch work" and clock out 1d for instance.
3. Go to Timesheet screen: the ticket does not appear, but the planning activity is displayed in a heading section "Work not assigned" (with the workload of 1d).
4. If I go back to the ticket, remove the work dispatched and then add back a new workload. THEN in the Timesheets, the ticket is displayed under the activity under the current project.

My question is:
In Timesheets, why the ticket is not showned the first time under the activity/project (=not in "work not assigned") ?

Also, when I do the same steps but as the Project leader, the ticket appears correctly in the timesheet...

Thank you for your help!


 
Posted : 28 Mar 2025 21H56
(@marylene)
Posts: 592
Contributor Admin
 

Hello

I'm not reproducing. Can you try reproducing on our demo instance? Are there any errors in the ProjeQtOr logs? In the browser logs?
Be careful with the behavior of tickets in allocations. The ticket appears correctly in allocations with actual work. and Unplanned.


 
Posted : 02 Apr 2025 12H16
(@john-k)
Posts: 2
New Member
Topic starter
 

Hello,
Thank you for your quick answer,

I cannot see any error in the browser logs (and I cannot access the server logs).
I reproduced my problem on the Demo environment, as recommended. Please check Timesheet for user "Member" with activity #12 and ticket #4.

To give more context, I'm gathering different dev/technical tasks (tickets) into a feature task (activity). So that I can have more details on the workload of the different parts of the feature, without having to create 1 activity per dev task.
A bit like in JIRA, where I would create a Story card for my feature and a Task card for the developments.

Best regards,


 
Posted : 02 Apr 2025 12H55
babynus
(@babynus)
Posts: 14966
Main Contributor Admin
 

Hi,

Very strange : I could not reproduce on local Dev instance, but could with excatly same steps on Demo.
Ticket #9929 recorded


 
Posted : 10 Apr 2025 19H27
Share:

Scroll to Top