Custom Fields Overview

What are Custom Fields?

Custom Fields are a part of the evolution of our Data Model that elevates the Shortcut experience for more structure, organization, and flexibility.

They were designed to help with the categorization of work and to help organizations transition away from Projects (if applicable to your Workspace). 

 

The following Custom Fields can be added to Stories, each with its own subset values:

  • Technical Area
  • Skill Set
  • Product Area
  • Priority
  • Severity

 

How to enable Custom Fields

    1. Click on your User Icon on the bottom-left area of your screen.
    2. Click Settings.
    3. Select "Custom Fields" under Workspace Features.
    4. Select Edit on the Custom Fields you'd like to enable for the Workspace and toggle the setting on.
    5. While the Name or Description cannot be edited, the values for each Custom Field can be modified.

Please note:

    • Colors can be configured for Technical Area, Skill Set, and Product Area by clicking on the color box next to each value.
    • For Priority and Severity, although each value can be renamed and disabled or enabled, the color and the order of the values or icons cannot be changed.
    • The Severity field will only show on Stories assigned as a Bug-type.
    • The Custom Fields on a Story dialog can be reordered by navigating to your Custom Fields Settings page.

custom-fields.gif

 

Custom Field Definitions and Default Field Values

The table below contains a breakdown of the Custom Fields available, their default definitions, as well as their default values. While you can't change the Field Type or Definition of these fields, you're free to remove and/or add Field Values as you please. (There is currently no limit to the number of field values that can be created).

 

Field Type Definition Default Value
Technical Area The location in the tech stack of this work
  • Web app
  • API
  • Mobile 
  • Server
  • Client database
Skill Set The skills or abilities needed to complete this work
  • Frontend engineering
  • Backend engineering
  • Product
  • Design
  • Analytics
Product Area The impacted area or feature within the product
  • Onboarding
  • Billing
  • Search
  • Integrations
  • Demo
  • Notifications
Priority Used to filter and sort Stories in order of priority
  • Highest
  • High
  • Medium
  • Low
  • Lowest
Severity

Used to filter and sort Stories in order of severity

  • Severity 0
  • Severity 1
  • Severity 2
  • Severity 3
  • Severity 4

 

Filter Views and Custom Field Types:

  • You'll find a list of Fields and their corresponding values on the Stories page sidebar menu just below Filters. Story_kanban.gif

     

    If viewing the Table View, you'll also be able to group by Custom Fields using the "Group By" dropdown menu. Fields_Story_page_Table_view.gif
  • Filtering Stories on the Status page can easily be done by accessing the Custom Fields dropdown menu. Fields_-_Status.gif
  • Filtering Stories on an Epic's detail page can easily be done by accessing the Custom Fields dropdown menu. In addition to filtering, you'll also be able to group by Custom Fields using the "Group By" dropdown menu.

     

    Fields_-_Epic_detail_page.gif
  • At the top of the Reports page, you'll find the Custom Fields menu along with all of the other filters.

     

    Fields_-_Reports.gif
  • Filtering Stories on an Epic's detail page can easily be done by accessing the Custom Fields dropdown menu. In addition to filtering, you'll also be able to group by Custom Fields using the "Group By" dropdown menu.

     

    Fields_-_Team_detail_page.gif

Where Custom Fields appear:

Story Cards

Fields_Story_card_view.png

Story Dialog

Fields_Story_Dialog__light_mode_.png

 

Custom Fields FAQ

  • All Organizations will have access to the following Fields:
    • Technical Area
    • Skill Set
    • Product Area
    • Severity 
    • Priority
    Only Organizations on the Business and Enterprise Plans will have access to Advanced Custom Fields.
    • Custom Fields help you establish a more structured process in your Workspace. Because Custom Fields and their values are controlled by your Admin - there is more structure to Custom Fields over Labels.
    • Labels are great because anyone in your Organization can create them, but they lack the structure of Custom Fields. You should use Labels as a lightweight but unstructured way to organize your work.

Seeking to Transition from Projects to Custom Fields?

Check out our Transition from Projects to Fields documentation here!

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request