aws-amplify / aws-amplify/amplify-hosting

Clicking on environment name is not intuitive for navigating to build history

Open
#567 0 comments 0 reactions 0 assignees View on GitHub
console feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**

My builds were failing to go through for a day. I kept trying to upload a new zip. Then thinking it might be smart and avoid re-deploying a binary identical zip, I tried making small modifications to force a new deploy.

I didn't see any details about past deploys. I finally figured out today I could click on the environment name to the the build history and cancel previous ones.

**Describe the solution you'd like**

It would be good to have a clear link like "build history" on the UI, unfortunately this is somewhat just a problem with modern web UIs, since we have abandoned using underlines to denote links, we end up having to mouse-over any bit of text on a page to find out if maybe it is a link, or maybe not and just happens to be a different color, which is also common for headings like this.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Research direction

Start by locating the environment name in the hosting web UI and inspect how it currently exposes build history. Done means the UI provides an obvious, clearly labeled way to reach build history without relying on clicking the environment name.

Written by the indexing model from the issue text.

Assessment

Domain
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.