Differentiate between "effort time" and "processing time"

Dear community

We are using YouTrack Standalone 2020.3.12000 and we have a question.

We have tasks that take a rather long time, but require little attention from the developer. For example, an automated test which runs for 3 days but takes only 1 hour to set-up, start and evaluate.

This kind of task should have an estimate effort of 1 hour, but a processing time of 3 days.
This should be visible in the Gantt report (3 days) but the assignee shall be blocked by the "Constraint" parameter of the Gantt report only for a duration on 1 hour.

Is this possible?

A similar question is the following one: can I define a task that shall be worken on by the developer with an effort of 50%? I.e., if the estimate effort is 5 d, then the expected completion date is in two weeks.

Kind regards, Enpa

Official comment


I'm Sergey from the YouTrack team. 

When it comes to the Gant chart, you can only use one field for the estimation, so it won't be possible to select one field which value is reflected in the task duration, while the other is used for constraints only, I'm afraid. The same applies to the work effort. 

Generally, though, outside of the Gantt chart, you can create as many fields as you wish and store any data there. Then use this data as needed, for example, retrieve it via REST API.

Also, I'd like to note that you can always contact the YouTrack support team directly via https://youtrack-support.jetbrains.com/hc/en-us/requests/new or youtrack-support@jetbrains.com

Thank you Sergey

I think we can generate tasks and leave them unassigned, so that they get planned concurrently. That should solve the problem.

We still have the issue with part time employees. Here the solution seems to be https://youtrack.jetbrains.com/issue/JT-38441
I voted for it, let's hope it will get implemented.

Kind regards, Enpa


Glad to hear that you found a solution for your first case. Hope it will work for you.

I voted for it, let's hope it will get implemented.

Thanks for your vote. That'd be the first step indeed. Then it'll have to be implemented in the Gantt chart, as I assume, your question was related to the Gantt chart first and foremost.


Please sign in to leave a comment.