You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow drag-and-drop reordering of environment variables in the "ENVIRONMENT VARIABLES" tab. (Similar UI functionality has already been introduced for reordering of job tasks and pipeline stages.) Over time, some pipelines may accumulate quite a number of variables, which are often simply added to the end of the existing list of environment variables. There is currently no method in the UI to reorder the list of variables, except to delete and recreate existing variables in the desired order, which is cumbersome and prone to error. Consequently, users just leave the list of variables in the order they were created, and the resulting order can seem random and lead to a confusing user experience.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.
Issue Type
Summary
Allow drag-and-drop reordering of environment variables in the "ENVIRONMENT VARIABLES" tab. (Similar UI functionality has already been introduced for reordering of job tasks and pipeline stages.) Over time, some pipelines may accumulate quite a number of variables, which are often simply added to the end of the existing list of environment variables. There is currently no method in the UI to reorder the list of variables, except to delete and recreate existing variables in the desired order, which is cumbersome and prone to error. Consequently, users just leave the list of variables in the order they were created, and the resulting order can seem random and lead to a confusing user experience.
The text was updated successfully, but these errors were encountered: