-
Improvement
-
Resolution: Won't Fix
-
Minor
When defining a workflow actually the most important part is the workflow part. However, to see it after clicking the job, you need to scroll down all the time. From an interface ergonomics point of view this is very cumbersome. The major information that shows up in the middle of the screen seems to be the 'Build Triggers', however the SCM information is buried somewhere in the workflow anyway. Ideas: Move 'Build Triggers' to the bottom, move all of the additional project configuration to the bottom and put the workflow on top.
tfennelly says in JENKINS-31585:
On having to scroll down the page to see the flow .... yeah, agree again. This annoyed me enough when I first experimented with the ACE Editor that I played with adding tabs to the config pages. I was able to do this (without breaking form submission) and so bring the user straight to the flow, while at the same time generally making it easier to use the config. See short 30 sec video.
- relates to
-
JENKINS-37183 Pipeline text area doesn't have a horizontal scrollbar when long lines are long
-
- Open
-
[JENKINS-31635] Eliminate need for scrolling when editing inline Pipeline script
Jens Wilke
created issue -
| Description |
Original:
When defining a workflow actually the most important part is the workflow part. However, to see it after clicking the job, you need to scroll down all the time. From an interface ergonomics point of view this is very cumbersome. The major information that shows up in the middle of the screen seems to be the 'Build Triggers', however the SCM information is buried somewhere in the workflow anyway. Ideas: Move 'Build Triggers' to the bottom, move all of the additional project configuration to the bottom and put the workflow on top. Feedback [[~tfennelly] from On having to scroll down the page to see the flow .... yeah, agree again. This annoyed me enough when I first experimented with the ACE Editor that I played with adding tabs to the config pages. I was able to do this (without breaking form submission) and so bring the user straight to the flow, while at the same time generally making it easier to use the config. See short 30 sec video. |
New:
When defining a workflow actually the most important part is the workflow part. However, to see it after clicking the job, you need to scroll down all the time. From an interface ergonomics point of view this is very cumbersome. The major information that shows up in the middle of the screen seems to be the 'Build Triggers', however the SCM information is buried somewhere in the workflow anyway. Ideas: Move 'Build Triggers' to the bottom, move all of the additional project configuration to the bottom and put the workflow on top. [~tfennelly] says in bq. On having to scroll down the page to see the flow .... yeah, agree again. This annoyed me enough when I first experimented with the ACE Editor that I played with adding tabs to the config pages. I was able to do this (without breaking form submission) and so bring the user straight to the flow, while at the same time generally making it easier to use the config. See short 30 sec video. |
| Assignee | Original: Jesse Glick [ jglick ] | New: Tom FENNELLY [ tfennelly ] |
| Summary | Original: Eleminate need for scroll down when editing a workflow | New: Eliminate need for scrolling when editing inline Pipeline script |
| Workflow | Original: JNJira [ 167069 ] | New: JNJira + In-Review [ 182570 ] |
| Component/s | New: pipeline-general [ 21692 ] |
| Component/s | Original: workflow-plugin [ 18820 ] |
| Component/s | New: workflow-cps-plugin [ 21713 ] | |
| Component/s | Original: pipeline [ 21692 ] |
| Link | New: This issue relates to JENKINS-37183 [ JENKINS-37183 ] |
This is very annoying and IMHO more important than just 'minor' issue.