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
    • Upgrade to Enterprise edition
    • 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

Content

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. Custom Field Unusable with community plan: cannot activate for workpackage type

Custom Field Unusable with community plan: cannot activate for workpackage type

Added by Giulia Conforto almost 3 years ago

I understand that custom fields are a feature also offered in the basic community plan. However, work package custom fields can be populated only after activating them for work package types, which is only a premium feature. This makes work package custom fields unusable, or am I doing sth wrong? Thanks!


Replies (3)

RE: Custom Field Unusable: cannot activate for workpackage type - Added by Giulia Conforto almost 3 years ago

Dear Betty, sorry but I don't understand how your comment is related to the issue I pointed at. Independently from who completes a work package, with a community plan, custom fields are unusable for work packages because they can only be activated once added to a work package type and this is only a premium feature. Can anyone please confirm or help me understand how to add a custom field to a work package with my basic community plan? That would be very much appreciated

Betty Anderson wrote:

Completion of a work package is most often overseen by a specific person: a manager, supervisor, a team lead, or a designated team member.

RE: Custom Field Unusable with community plan: cannot activate for workpackage type - Added by Allison Woolbert almost 3 years ago

Totally get the frustration on this - It's a little convoluted.  I tried to recreate what I did in order to bring those for use in a project.  I think I got all the steps, but if not, just ping me back and I'll see what I missed.

1. Go to administrator

2. Go to Custom Field

3. Go to Work packages

4. Click Custom Field

5. Enter Data for a custom field

6. Go to  Administrator /  Work packages 

7. Check off the Display by Default on the new field. (Under Customize the Appearance of the Work Package List

8. Go to Work Package Types

9. Activate the field under Form Configuration (Drag-n-Drop the filed from INACTIVE to a section on the left.

10. Go to a Project

11. Go to Project Settings

12. Go to Custom fields

13. You can then activate a custom field in the project

RE: Custom Field Unusable with community plan: cannot activate for workpackage type - Added by Giulia Conforto almost 3 years ago

Hi Allison,

Thank you so much for your help, I got it now! I had followed the exact same steps and was facing the same issue. So, to take a snapshot of the page that indicates how the form configuration of work package types is a function only available for enterprise plans, I zoomed out to 50% and bam! I just saw that the drag and drop area was just below, where I could not see it. So this was no bug, just me not knowing it was enough to scroll down to access the drag and drop configuration area :)

Thanks!
Best,
Giulia

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