Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. General discussion

Activating custom fields

Added by Alex Fantini 17 days ago

Good morning everyone,
I am a new user of software for task management in different departments of a student association.

Using the Custom Fields feature, I think I have noticed a behavior that is different from what is described in the documentation (as I understand it) and in my opinion inconvenient.

When I create a non-global custom field, I have to activate it in a project and put it in the form of at least one work package. Here is where the problem arises: when I show the field in a work packages (e.g., task) it is automatically activated in all projects that have that type activated even though the custom field was previously disabled for them.
To date, the only workaround I have found is to then disable the custom field manually for each project where it is not needed. The same problem actually occurs with new projects (the custom field is immediately active) and that is why I have not found a solution yet.

The documentation I am referring to is this.
I do not classify the discussion as a bug because I am not sure it actually is one, in case I will provide more specific information on version and steps to reproduce the problem.

Thank you
Alex


Replies (2)

RE: Activating custom fields - Added by Alexander Stock 17 days ago

Hello Alex,

you will be glad to hear that this will change with with the upcoming release:

Hence, I encourage you to update to the next major release as soon it is available (this month) so that adding custom fields in instances with many projects will be more comfortable.

Best,

Alexander

RE: Activating custom fields - Added by Alex Fantini 17 days ago

Perfect, thank you very much!
In searching I had not seen this feature, I will definitely update.


Thank you
Alex

  • (1 - 2/2)
Loading...