getsentry / getsentry/sentry

Customer Feedback: Usability Issues in the Workflow notifications settings page

Open
#61,985 5 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Settings Projects
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

Feedback Provided by Customer:

1) The "Settings for Organization" heading confused me. Initially I thought it was a setting that affects all colleagues using Sentry and not a personal setting so I didn't want to change it. Looking more closely, I think this is in fact a personal setting (looking at the breadcrumb that includes the word "Account"). This could use a better label
2) Adding a project-specific setting requires pressing the purple "+" button (see screenshot). Initially I navigated away from this page without pressing the "+" button, since I thought this button was used to add another row to this table, when it's actually used to submit the current row. I'd recommend changing this to a verbal CTA like "Save", as well as preventing navigating away from the page if there's unsaved form data locally.

### Solution Brainstorm

_No response_

### Product Area

User Feedback

Contributor guide

Open the contributing guide

Research direction

Start by locating the Workflow notifications settings page and reviewing the current “Settings for Organization” heading and purple “+” control described in the issue. Done means the personal-setting label is clearer, the project-specific action uses an explicit save CTA, and navigating away with unsaved form data is prevented.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.