Yes. While we're considering ways to more smoothly handle time changes (such as by working with time zones instead of UTC offsets), currently an Organization's UTC offset needs to be manually updated by an Organization Owner or Admin whenever Daylight Savings Time begins or ends. If you're an Owner or an Admin, you can update your Organization's UTC offset to reflect DST by going to the settings gear wheel and then Workspace Settings > General Settings. This setting affects all dates and times in Clubhouse. You may also want to double check and update your user account's UTC offset while you're there, found in Settings > Your Account > Your Profile. This setting affects the dates and times in notification emails that you receive from Clubhouse.
Not for now. We've found that custom fields have the ability to cause users more problems than they solve, but we are tracking this request internally.
Currently, priorities in Clubhouse are structured vertically in a workflow state column. The higher up in the column the Story, the higher its priority. By default, newly created Stories populate at the bottom of their assigned workflow state column, and they can be dragged up or down to change their priority.
What we often recommend to Organizations, in tandem with our default priority system, is to use Labels (or for Milestones, Categories) to show or manage custom priorities on Stories and Epics. For instance, at Clubhouse, we use severity labels to denote how urgent a reported or internally found bug is.
Although Milestone categories are used to make grouping and filtering Milestones easier, the benefit to using labels on Stories and Epics is that each label has its own page and reporting in Clubhouse. You and your team can see all Stories and Epics with that label and track progress on them as well. Clubhouse also has Quick Filters and Spaces on the Stories page, which allows you to zero in to labeled Stories fast and easily.
Clubhouse was designed to get numerous teams on the same page and on one board. However, we understand that sometimes the workflow of one team is drastically different than another.
The first step is to create your Teams in Clubhouse. Projects currently link to Workflows but we are actively designing a Team-to-Workflow relationship that will allow you to customize and automate your Workflows by Team. We know there is a natural connection between a Team and their process (aka their Workflow), so we want this reflected in Clubhouse.
For now, you can use our Workflow feature to keep custom workflows separate but still maintain visibility and nurture collaboration across the entire organization. Get started with Workflows here!
Note that Projects can be used for further classifying work by component, focus area or product. If you do not have a need for this level of categorization, we recommend using a single Project for a Workflow.
We currently limit the size of attachments uploaded from a computer to Clubhouse to 50MB. However, we don't impose any size limits to attachments uploaded from a cloud storage service, so if you have a Dropbox, Google Drive, or Box account, you should be able to attach large files from there.
We are continually trying to strike a balance between flexibility and simplicity in our UI/UX, and from our experience we’ve found that managing user permissions can quickly get complex and confusing. For this reason, permissioning is currently only supported at the Workspaces level.
Also, not to worry: you can have unlimited Workspaces with no additional charge. We count users at the Organization level, which means that you are billed for the total number of users in your Organization (past 10 users, of course), regardless of how many Workspaces they are members of. Inviting guests as Observer users (which are free and unlimited to paid subscriptions) might also be a good option for providing visibility to your work.
Every organization has at least one project. Projects represent any open-ended product, focus area or component. The most effective use cases for a Project are functional area (frontend, backend, etc) or component (API, web app, etc). If you do not have a need for this level of categorization, we recommend using a single Project for a Workflow. Projects don't have a defined start or end date, and every Story in Clubhouse must be associated with a Project.
An Epic is a collection of Stories (individual pieces of work) that together make up a larger initiative that your Workspace is working on. An example of a large initiative would be the release of your organization's first mobile app. Due the nature of this, Epics have a start and an end date.
Epics and Projects are not similar, but there is a relationship between them in that an Epic can be indirectly associated with a Project (or Projects, as the case may be) through the Stories in that Epic.
We don't offer an on-premises/self-hosted version yet. However, we are tracking interest in this, and we'd love to hear from you about your company's requirements for a self-hosted version of Clubhouse.
Projects represent any open-ended product, focus area or component. The most effective use cases for a Project are functional area (frontend, backend, etc) or component (API, web app, etc). If you do not have a need for this level of categorization, we recommend using a single Project for a Workflow. Projects don't have a defined start or end date, and every Story in Clubhouse must be associated with a Project.
Milestones are a collection of Epics. Milestones are meant to provide a timeline view of your work, and to help with long-term planning. These also tend to have defined start and end dates.
Currently only members of your Clubhouse Workspace are able to access or view your Clubhouse content. We offer Observer (read-only) roles, which are free to Organizations on a paid plan. If you'd like to give access to specific information, we recommend creating a new Workspace, adding the information there, and then inviting Observer users to that Workspace as you like. This might be a good way to give others visibility into what you're working on while we consider this feature.
We currently have an integration with Zendesk available.
We do have long-term plans to fully integrate with other popular help desk tools such as Help Scout, Intercom, Freshdesk, etc. For now, users with other help desks can still utilize the "External Tickets" field.
You can add tickets from those help desks within the Create Story and regular Story dialogues. Adding a ticket link will automatically populate the help desk's icon and name to lessen confusion as well. Example:
This is a great way to link support tickets to your Stories.
Building integrations around time tracking tools is something we plan to work on. There are third-party time tracking tools that currently integrate with Clubhouse, like Toggl and Clockify, which work via a Chrome or Firefox extension. If you want to suggest that we integrate with your favorite time tracker, drop us a line!
The Clubhouse web experience (https://app.clubhouse.io/) is supported with the latest three versions of these desktop web browsers:
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
Our mobile web experience also supports:
- Safari (iOS)
- Chrome (Android / iOS)
- Firefox (Android / iOS)