argoproj / argoproj/argo-workflows

UI: Add hover-over text for ambiguous buttons

Open
#9,541 7 comments 2 reactions 0 assignees View on GitHub
area/retry-manual area/shutdown area/suspend-resume area/ui solution/suggested
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 15h
Merged PRs (30d)
138

Description

# Summary

Documentation and UX need to make it clear how `retry` and `resubmit` differ.

![image](https://user-images.githubusercontent.com/2119212/188985152-67245a12-9c4b-4e7c-b9da-34f448f3760b.png)

https://argoproj.github.io/argo-workflows/cli/argo_retry/

> argo retry[¶](https://argoproj.github.io/argo-workflows/cli/argo_retry/#argo-retry)
retry zero or more workflows

```
argo retry [WORKFLOW...] [flags]
```

https://argoproj.github.io/argo-workflows/cli/argo_resubmit/

> argo resubmit[¶](https://argoproj.github.io/argo-workflows/cli/argo_resubmit/#argo-resubmit)
resubmit one or more workflows

```
argo resubmit [WORKFLOW...] [flags]
```

# Use Cases

Someone trying to understand when to use `retry` and when to use `resubmit`

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start with the linked argo retry and argo resubmit command documentation and compare their described behavior with the attached UI screenshot. Locate the UI entry points for these two actions, then define hover text that clearly distinguishes when to use each; done means users can tell the difference without consulting separate documentation.

Written by the indexing model from the issue text.

Assessment

Domain
design, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.