Comply with your company's Corporate Identity and communicate it to stakeholders. With a custom theme you can upload your own logo and define colors for the header navigation, side menu, as well as links and buttons.
Your custom theme is automatically responsive: It is not only visible on desktop but also on mobile devices, such as tablets and smartphones.
In the administration you can easily customize your OpenProject theme: Upload a logo, a custom favicon and define custom colors. You can even set a custom touch icon to be used on your tablet or smartphone.
Many different styling options provide you a lot of flexibility when customizing your OpenProject custom theme and logo. You can easily and rapidly adjust your theme at any time. If you made a mistake, you can reset the theme with one click.
OpenProject Single Sign-On reduces the hassle of keeping track of numerous ID and password combinations, also saving time you would spend re-entering credentials for the same identity. OpenProject supports the main authentication provider such as CAS, SAML, OpenID Connect, and Kerberos.
Work package attributes are combined into separate groups (e.g. Details, People, Estimates & Time). Depending on the use case the default groups and attributes may not always be the best fit. Use work package forms to customize the attributes shown for each type.
By default, the same attributes are shown for all work package types, such as Phases, Milestones, Tasks or Bugs. Often, this is not what you want. The start and due date may be relevant for Phases and Milestones but quite possibly not for Bugs.
As an administrator you can customize the types and define which attributes (including custom fields) are shown for which types. As a user of the Enterprise Edition you can also define attribute groups to further customize work package types.
Attribute groups work as headings and containers for attributes that fit together logically. By creating your own attribute groups you can directly communicate what certain attributes are about.
By creating an attribute group Customers for example, you communicate to your team members that attributes in this group concern your clients. Remove attributes that are unimportant and freely define the order in which attributes are displayed.
Once you adjust a work package type (such as type Task) the defined attributes and attribute groups are shown for all work packages of this type.
By setting descriptive attribute group names, project members see right away which values to set.
You can even customize work package types to show very few attributes or show only custom field attributes.
With this option, you can hide all non-essential information and communicate effectively with your team.
As a user of the Enterprise Edition, you can create multi-select custom fields for work packages (either of type List or of type User). Other criteria, such as required status, filter or searchable remain unchanged.
On the work package which uses the custom field, simply assign one or multiple values to the work package. The multi-select option allows you to select several options at once.
To enable multi-select, simply choose the multi-select button when creating a custom field.
Let's take a look at an example:
If a company develops products for multiple customers and creates a work package custom field Customers to track which customers are interested in a product, it makes sense to be able to choose multiple values for the Customers custom field.
The same applies for filtering work packages: You can filter for individual values as well as for multiple values.
In the example, this allows you to display all requirements that two of your customers have.
With the Enterprise Edition you can add relation columns directly to the work package list.
This gives you an overview of the relations for all displayed work packages.
The column will display a number of work packages that have a certain relation to the work package. By clicking on the number you can expand the list and see the work packages that have the specified type of relation with the work package.
Simply open the work package column modal and select the relation you want to display in the work package list.
You can either display the type of relation (e.g. blocked by, follows) or the type of work package that is related (e.g. Task, Milestone, Phase).
Use Case 1: Feature development
When you develop new features and test those features prior to a release you may find some critical bugs. In order to prevent buggy features from being released, you can create a blocked relationship from the bugs to the feature.
This prevents the feature from being closed without the bugs being closed first.
To get an overview of the features and the bugs that block the release of those features, simply filter for the features and add a Blocked by column to the work package list.
You now have a compact overview of the features and the bugs blocking the release of those features. To see which bugs are blocking a specific feature, simply click on the number shown for the feature in the Blocked by column. This expands the list of bugs.
Use Case 2: Release management
When you plan new releases, it is important to see which work packages are required for the releases. Showing this information is easy.
Simply create an includes relationship between the work packages in the release and the release itself. From the work package page you can then easily see which work packages belong to a release and how many have been completed.
Especially when you have many custom fields it is sometimes unclear what certain attributes entail and what information users should enter.
Create and manage help texts for attributes in the work package forms. Choose the fields which need additional explanation. Within the help texts you can specify exactly what is meant and what the user needs to do.
This is very helpful for complex projects with several specific work package forms and multiple custom fields. Especially new users become familiar much quicker with the work package forms. Furthermore, you reduce the number of mistaken or wrong entries.
As a user of the Enterprise Edition, you can specify attribute help texts in the administration.
You can select any work package attribute (including custom fields) and specify the description which is shown to project members.
Use the wiki syntax to format the help text, for example to enter headlines or lists. You can also enter links, for example to additional documents or company guidelines.
On the work package page a questions mark - shown next to attributes - indicates that a help text exists for an attribute. Project members can simply click on the question mark to show the description for the attribute (defined in the administration).
As an admin you can edit attribute text field descriptions on the spot, e.g. to make adjustments or correct errors in the description.
