Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve ops UX through job/resources renamings #228

Open
gberche-orange opened this issue Jan 8, 2019 · 1 comment
Open

Improve ops UX through job/resources renamings #228

gberche-orange opened this issue Jan 8, 2019 · 1 comment

Comments

@gberche-orange
Copy link
Member

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

The current naming for jobs is sometimes not explicit. E.g. #11 for tf or #218 with a new "hard-reset"
This impacts user experience for service operators, especially as concourse does not support adding documentation to jobs.

Describe the solution you'd like

A consistent naming for jobs/tasks/resources, which makes sense from user perspective.
@o-orand o-orand added this to the 4.0 milestone Jan 18, 2019
@poblin-orange poblin-orange mentioned this issue Jun 5, 2019
Open
10 tasks
@o-orand o-orand modified the milestones: 4.0, 5.0 Jul 9, 2019
@o-orand o-orand modified the milestones: 5.0, 5.1 Oct 8, 2020
@o-orand o-orand modified the milestones: 5.1, 5.2 Dec 14, 2020
@o-orand o-orand modified the milestones: 5.2, 5.3 Nov 22, 2021
@o-orand o-orand removed this from the 5.3 milestone Jan 4, 2022
@o-orand
Copy link
Member

o-orand commented Jan 4, 2022

With current COA usage, I'm not sure this is our priority.

@o-orand o-orand moved this to P1 in CF OPS Automation Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
CF OPS Automation
Status: P1
Milestone
No milestone
Development

No branches or pull requests
2 participants
@o-orand @gberche-orange