Keep your conversations more focused. LearnallaboutournewThreadedComments.

Fields are here for better categorization, structure, and organization of work

Tiffany Go

Fields are here to help with the categorization of work and to help organizations transition away from Projects.

The Fields release is the next step in the evolution of our Data Model that elevates the Shortcut experience. Our goal is to provide enough structure to organize, but also enough flexibility to let you represent your work and processes in Shortcut the way you like to work in real life.

The initial Fields release allows you to add the following Fields to Stories:

  • Technical Area
  • Skill Set
  • Product Area

Next we’ll add Severity and Priority. More on that later in the post.

An Intro to Fields

Watch this video to get started with Fields!

Start using Fields to replace Projects

Projects provided some level of organization within Shortcut, but it was often unclear how to exactly use Projects. Hearing from customers that Projects were confusing, we decided to begin the journey to remove Projects and improve the Data Model.

Eventually, we will allow you to toggle Projects off for your workspace before finally removing them completely from Shortcut. We want to get Fields in your hands as soon as possible to enable you to begin thinking about what your Workspace could be without Projects. We're eager to hear your feedback as you start this transition and learn what improvements need to be made before you would be comfortable removing Projects.

Transition from Projects to Fields

Start using Fields to replace Projects

Coming soon…improvements to Bulk Editing

We plan on releasing updates to Bulk Editing to support massive volume at once to help make the transition even easier! At this time we recommend limiting bulk editing up to 500 Stories at a time.

What you can do with Fields

All Fields are single-select drop-downs. Fields are set at the Workspace level and will be enabled by default for all new customers. For existing users (as of February 23, 2022) only Admins will have the ability to enable or disable them, as well as configure the values and colors.

Where it appears in the app:

  • Story Cards 
  • Individual Stories

Filter by Fields on the:

  • Stories Page 
  • Report Page
  • Epic Detail Page
  • Teams Page
  • Status Page

Note: We're working to add these columns to Story Tables throughout the app.

Shortcut Fields

Field Definitions and Default Field Values

Field Definitions and Default Field Values

Advancing the Shortcut Data Model

As we transition away from Projects to improve the Data Model the introduction of Fields helps replace the Project use cases. Check out this article for a step-by-step guide on How to Transition from Projects.

During our research, we found that Projects are being used for 2 main use cases:

  • Teams 
  • Categorization

The first step to removing Projects was to build a first-class Teams feature (you can read more here.) The second step is to solve for the Categorization use case, and we’re beginning with Fields.

Fields allow you to categorize Stories by common, Shortcut defined, dimensions: Technical Area, Skill Set, or Product Area. We found that these are the most common categorization use cases and wanted to solve for them first. An important difference (and improvement) over Projects is that you can apply as few or as many Fields to each Story, which allows for more complex and nuanced Story data. While the Field names can’t be changed, you can adjust the values to fit your need. We understand that your Team and process might not align with these 3 fields, so we’re also building Custom Fields so you can truly customize Shortcut to fit your process.

Fields will enable you to denote the dimensions and details that are most important to your Team's processes. With the control Fields in the hands of Admins, you’ll be able to create and enforce more consistent processes to make sure Stories have the data they need. Now stories can be more nuanced and have multiple Fields to better represent the true complexity of your work.

Coming soon… Severity and Priority Fields and Custom Fields

Severity and Priority will be our next Fields release.

Custom Fields will allow you to define Fields names and values to fit your process.

Stay tuned for more details and attend our February Release on 2/23 for more information.

Fields FAQs

What is the difference between Fields and Custom Fields?

Fields are Shortcut defined and the Field name and description cannot be changed. The values associated with Fields can be changed. Fields have been initially developed to help our customers move away from Projects.

Custom Fields will allow you to define Field names and values to fit your process.

Who will have access to Fields?

All plans will have access to the following Fields:

  • Technical Area
  • Skill Set
  • Product Area
  • Severity (not yet released)
  • Priority (not yet released)

Who will have access to Custom Fields?

Team, Business, and Enterprise customers will have access to Custom Fields, more details will be shared when Custom Fields are released.

Free and Legacy Standard customers will not have access to Custom Fields

How are Fields different than Labels?

Fields help you establish a more structured process in your Workspace. Because Fields and their values are controlled by your Admin - there is more structure to Fields over Labels.

Labels are great because anyone in your Organization can create them, but they lack the structure of Fields. You should use Labels as a lightweight but unstructured way to organize your work.

More stories from Shortcut