Hello, I am trying to set a custom field in the projects to represent my The customer, so that later I can filter by customer all the Work packages. Apparently it is not possible today. any ideas?
did you maybe not set your custom field as "Used as a filter"? You need to check this box to be able to use your custom field as a filter. [1]
You might also have created a custom field for a different module (Projects, Users etc.) and thus it can not be added to your work packages.
Please also keep in mind that custom fields need to be activated per work package type and per project.
Thanks for your reply @Alexander I did do all those things, I can filter by custom field if I set the custom field on the work packages, it is not practical to have to set and repeat the same field (The project's customer) on all hundreds of Wp's. What I was trying is to add the custom field to the project settings. And thus latter on filter all the workpackages whose project's custome field is x.
so all work packages in a project have the same customer? If so, you could name the project after your customer or include an identifier (purchase order...) directly into the projects name. With the global project lists, you can filter on the project name. Additionally, you can also create a custom field for a project. That custom field than appears when you create a new project (advanced settings)
An example:
You create new custom field for projects called "customer id". [1] Each time you create a new project, this field can be filled with a number.
With the global projects list, you can filter for this number and instantly see the belonging project with its work packages. [2]
Replies (3)
Hello Dive Bert,
did you maybe not set your custom field as "Used as a filter"? You need to check this box to be able to use your custom field as a filter. [1]
You might also have created a custom field for a different module (Projects, Users etc.) and thus it can not be added to your work packages.
Please also keep in mind that custom fields need to be activated per work package type and per project.
Best
Alexander
[1] https://www.openproject.org/docs/system-admin-guide/custom-fields/#add-a-new-custom-field
[2] https://www.openproject.org/docs/system-admin-guide/custom-fields/#assign-a-custom-field-to-a-work-package-type-and-project
Thanks for your reply @Alexander I did do all those things, I can filter by custom field if I set the custom field on the work packages, it is not practical to have to set and repeat the same field (The project's customer) on all hundreds of Wp's. What I was trying is to add the custom field to the project settings. And thus latter on filter all the workpackages whose project's custome field is x.
Hi Dive Bert
so all work packages in a project have the same customer? If so, you could name the project after your customer or include an identifier (purchase order...) directly into the projects name. With the global project lists, you can filter on the project name. Additionally, you can also create a custom field for a project. That custom field than appears when you create a new project (advanced settings)
An example:
You create new custom field for projects called "customer id". [1] Each time you create a new project, this field can be filled with a number.
With the global projects list, you can filter for this number and instantly see the belonging project with its work packages. [2]
[1] https://www.openproject.org/docs/system-admin-guide/custom-fields/custom-fields-projects/#create-a-custom-field-for-projects
[2] https://www.openproject.org/docs/user-guide/projects/#projects-list