Skip to content

FLOW-2350: Change Draft PR lozenge color to neutral grey in dev sessions list - (Jira Coding Agent)#1876

Open
atlassian[bot] wants to merge 1 commit into
mainfrom
FLOW-2350-change-the-draft-pr-lozenge-to-grey-1ea7b
Open

FLOW-2350: Change Draft PR lozenge color to neutral grey in dev sessions list - (Jira Coding Agent)#1876
atlassian[bot] wants to merge 1 commit into
mainfrom
FLOW-2350-change-the-draft-pr-lozenge-to-grey-1ea7b

Conversation

@atlassian

@atlassian atlassian Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

This pull request updates the visual presentation of pull request status labels in the Development section to improve clarity and user experience.

Key changes:

Change Description
UI Update for Draft PR Lozenge Changed the "Draft PR" lozenge background to a neutral grey (--vscode-badge-background) for better visual distinction.
Label Text Updates Display "Draft PR" for draft pull requests and "Open PR" for non-draft open pull requests, replacing raw state text for these cases.
Tests Added Added comprehensive tests to verify the correct display of "Draft PR" and "Open PR" labels and their styles, as well as fallback to raw state text for other states like "MERGED".

These changes enhance the clarity of pull request statuses in the UI, making it easier for users to quickly identify draft and open pull requests with consistent and visually distinct labels.


Rovo Dev code review: Rovo Dev couldn't review this pull request
Rovo Dev does not review pull requests created by bot accounts.

- Draft PRs now display 'Draft PR' with neutral grey background
  (--vscode-badge-background) instead of the green open PR color
- Open PRs now display 'Open PR' for better visual distinction
- Non-open states (MERGED, DECLINED, etc.) continue to show raw state text
- Added tests for Draft PR, Open PR, and Merged PR label rendering

Co-authored-by: Jade Jiang <jjiang2@atlassian.com>
@atlassian-cla-bot

Copy link
Copy Markdown

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
a393d78c-73d8-4f4d-84ea-500a2d3d8fc3@connect.atlassian.com

Already signed the CLA? To re-check, try refreshing the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants