Project

General

Profile

Custom fields with default values per project

Added by user 89237 3 months ago

Hello.

Is there a way to have a custom field and define a "default value" for it in each project?

I have several projects with different structures and custom fields. Some projects (Type 1) represent Applications and have subprojects for each module of an app, other projects (Type 2) have one subproject per customer. I want to add a "customer" field and define in each project (of the 2nd type) which customer it is associated to, in order to be able to retrieve Time Spent on each project per Customer. Is there a way to achieve it?


Replies (10)

RE: Custom fields with default values per project - Added by user 89237 3 months ago

Let me rephrase it, to be more clear:

I want to add a global "Customer" field and in each project of the 2nd type, define as a default value the Customer it is associated to, in order to be able to retrieve (for all projects) Time Spent on each project per Customer. In Type 1 projects, the user will manually fill-out this field.

RE: Custom fields with default values per project - Added by user 89237 2 days ago

That seems to work just fine! Many thanks for the plugin, does exactly what i wanted.

Hope i'm not asking too much but i would like to know if the following can be achieved (either forcefully or perhaps by a checkbox in the "default values" tab, which would be the best): a way to disable the custom fields of a project that DO have a default value defined, so that the user is not able to change this value.

RE: Custom fields with default values per project - Added by Sven Culley 2 days ago

This should be possible with the workflow, there you can disable fields per role

RE: Custom fields with default values per project - Added by user 89237 2 days ago

Yes, but this is defined on a specific tracker for ALL projects, right? I'm asking if a custom field can be disabled per project and only if a default value has been defined for it (in that project).

RE: Custom fields with default values per project - Added by Sven Culley 2 days ago

If there is a default value within the project

  1. Disable the field so nobody is able to change it
  2. Disable the field on a role basis

What about inherited field values from the parent project?

RE: Custom fields with default values per project - Added by user 89237 2 days ago

Well, in my case "inherited" should also mean "inherit the value defined at the parent level".

RE: Custom fields with default values per project - Added by user 89237 2 days ago

Done. Hope the description is clear enough. Thanks for keeping up with this, it's pretty useful to me.

    (1-10/10)