TimeTracking - open ended tasks that will never be closed

I am using the time-tracking features, which are great, but they don't easily support "open ended" acivities. Basically tasks that are not directly associated with an issue.

For example - time spent in meetings, time spent doing system administration (upgrading servers etc), time spent on general support.

I would like to track the above time categories, but I don't want to create a new issue ticket for each meeting. The best I have been able to come up with is creating some new issue types - "meeting", "system admin", and then having a couple of generic issues like "weekly project meeting" that just get time assigned to them, but never get closed.

Is there a better way?   I suppose I could use the workflow editor to block those issue types from ever being closed, but that seems a bit overkill.

1 comment
Comment actions Permalink
Official comment

Hello David,

Thank you for reaching out. Generally, your idea is the best option here. You can also make these tasks recurrent - e.g. "Weekly Project Meetings July", "Weekly Project Meetings August", etc. In this case, you'll be able to close them each month. Such issues can be created automatically using on-schedule workflows (example: https://www.jetbrains.com/help/youtrack/devportal/generate-issues-automatically-workflows.html#generate-issues-on-schedule).

Also, you can have separate projects to track issues like that. E.g. project Meetings that contains only issues related to meetings. This may simplify the process as you can simply remove the resolved states for such projects so that nobody can resolve any issue in the project. 

Hope it helps. Please let us know if you have any questions, we'll be happy to help. 

Please sign in to leave a comment.