Use standard terminology for project management

Important

Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned

Enabled for Public preview General availability
Users, automatically Mar 1, 2024 Apr 2024

Business value

We're making it easier to work with project accounting by updating the terminology we use for its features in the product and documentation. Specifically, we're renaming things that were called “jobs” to “projects.” The goal is to improve the user experience, the clarity of the documentation, and the consistency of the terminology across the application.

Feature details

For a long time now, we’ve referred to project accounting features as “jobs,” which has caused confusion in our community because that’s not the term that people who work with project accounting expect. We’re happy to announce that we’re addressing this legacy problem. To clarify the true nature and purpose of the project accounting features for various types of businesses, we’re replacing the term “job” with “project” in the user interface and documentation.

For example, entities such as job tasks, job journals, and job planning lines are now project tasks, project journals, and project planning lines. The renaming won’t break existing integrations and customizations because we’re only updating the captions in the user interface and the terms in our documentation. We aren’t touching the names of the underlying table and field objects.

Jobs being renamed as projects

Tell us what you think

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.