What are Projects?
Projects typically map to collections of people (such as Frontend, Backend, Mobile, Devops, etc) but can represent any open-ended focus area, product, component, or initiative.
Before the introduction of Teams, we encouraged the use of Projects as a way to categorize work by groups of users. Now that Teams and Workflows can be assigned to each other, we've decided to make Projects optional.
When creating a Story, you no longer need to assign a Project and can now leave it blank if you choose to!
Although Projects are now optional, they are still associated with Workflows. When creating a Story, selecting a Workflow will filter the available Projects to only those associated with the selected Workflow.
We envision Projects to be used as an optional form of further categorizing Stories. When areas of work become increasingly diversified, Projects may be a useful tool for some teams!
What is the future of Projects?
We recognize that there is a need for certain categorization to span various dimensions, which is why Projects can be so useful. However, Projects come with their own limitations and inflexibilities, so that's why we're designing Custom Fields which will be a more powerful and flexible alternative to Projects.
Want to see Projects in action? Explore our Sample Workspace, which contains pre-filled information that will allow you to see how it all works together. Access it by clicking on your Graduation hat on top right > Sample Workspace.