Have time tracking standard on every project

[Alexander De Leeuw]

Hi,

We would like to track time on every project. When we set up a new project, we always configure it in the project itself (by going to 'create issue', 'configure' and adding the 'time tracking' field.)

When we set up a new project, we have to configure this exactly the same way.

For example, we configured project X to have time tracking appear on every issue made. When we create a new project Y, we have to configure the time tracking again.

Is there an easier way to do this? Multiple efforts going into settings and browsing forums didn't work.

Thanks in advance!

[Walter Buggenhout · Accepted solution]

Hi @Alexander De Leeuw,

I assume you have already checked out the documentation on time tracking on this page. If not, definitely look into the sections on permissions and enable time tracking in projects.

I would like to add there is a big difference between team managed (next-gen) and company managed (classic) projects.

Team managed projects have their own configuration by design. As of now, they don't share settings with other projects, which automatically leads to the situation where you have to configure them separately for each and every project.

For company managed projects, the documentation points towards field configurations. Maybe even more important is your screen configuration: you can set up your default screens and use screen schemes and issuetype screen schemes to share that configuration with new projects you create.

In case you don't know:

• every issue can be created / edited / viewed. For each operation, you can define a screen with the fields you want to make available to your users.
• these screens are associated with an issue type. It is perfectly logical that a story has different custom fields than e.g. an invoice. So you group the screens for those operations in a screen scheme per issue type. 
• as a project can have multiple issue types, you then again group those screen schemes into an issue type screen scheme.

For a more detailed description, look into the documentation.

Once you have defined your perfect project, use it as a template for next projects. When you hit the create project button next time, select the option share settings with an existing project and your new project will use those same, default schemes you invested some well-spent time on. 

[Alexander De Leeuw]

Hi @Walter Buggenhout 

Thank you for your answer. We are indeed working on next-gen kanban projects.

So I guess the third paragraph answers our question.

Thanks again.

[Walter Buggenhout]

Great to hear! If the answer was indeed helpful, could you also mark it as accepted? That makes it easier to find for people having similar questions!