# Feature DREAM-972 - Info popovers that provide helpful explanations to complex or confusing terms and settings

Project: Stream Design System
Status: in specification
URL: https://community.openproject.org/work_packages/DREAM-972

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| DREAM-973 | Task | Identify a first set of relevant features and write explanations for each | in progress |  |  |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/8AGZbGT9OasvlW1x0z4ufu/Explanation-Popovers?node-id=0-1 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer | Aylin Paçaci |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

#### Why

OpenProject is a complex tool that offers a deep level of configuration and customisation. 

A small team can use it for collaboration and organisation using just work packages, the Gantt view and perhaps documents. A seasoned project manager or an administrator can go deep and use advanced features: integrations, complex filters, custom actions, scheduling with lag, MCP server, workflow automations.

Because we have to cater to this wide variety of users, parts of our interface can be quite confusing to some. Perhaps they aren’t familiar with certain concepts (like “Lag” when scheduling), don’t have domain knowledge in project management (to understand phases/gates) or simply don’t need that level of complexity (delegating selecting project-specific values to List custom fields to project admins).

**Wouldn’t it be nice if our software were friendlier and helped all users understand terms that might be confusing?**

**ℹ️ If you have thoughts on which terms need better explanation, please add them to the list:** <mention class="mention" data-id="81246" data-type="work_package" data-text="##SE-696" data-display-id="SE-696">\#\#SE-696</mention>

#### What

Create a new UX pattern where we add a small info (i) icon next to terms, options and settings that might be confusing.

When the user clicks on it, she sees a small popover with a easy-to-understand explanation of what it is, along with a link to the documentation.

<img class="image_resized op-uc-image op-uc-image_inline" style="width:643px;" src="/api/v3/attachments/925365/content">

#### Result

  - Less frustration and confusion for users

  - A friendlier, more accessible more interface

  - Our users learn things along the way, simply by using our software

  - More users discovering our documentation

#### How

During Passion Time:

  - We define the ‘Help Info Popover’ pattern using Primer’s existing [**Popover**](https://primer.style/product/components/popover/) component

  - We identify places in OP where this would be useful, across all features

  - We prepare texts and links to existing documentation

  - We add them within the two weeks

  - We document this new pattern in Lookbook

#### But why during Passion time?

Why not just do this in our regular dev time, you ask? Excellent question. Here's why:

  - It's a small feature that can be started and ended in two weeks

  - Passion time cuts across teams and streams; OP colleagues who work with, developed, tested or train users on different features can all bring their own suggestions for where this might be useful.

  - In just two weeks, we could improve the user experience of OpenProject in a meaningful way

  - Virtually no chance of feature creep. We add the popovers to where a fixed set of identified places and end with a pattern that any team can use thereafter.

  - Cross-pollination: works brilliantly with the on-boarding passion project: \#\#SE673

<br>
