-
New Feature
-
Resolution: Fixed
-
Minor
-
None
It'd be nifty if the jobconfighistory plugin could add a field in the job config form for a "change message" - since we're storing history of job changes, having somewhere to record a comment as to what the reason for the change is.
- is related to
-
-
- Open
-
-
JENKINS-43274 Add field to Job Configuration UI for change comment
-
- Open
-
-
-
- Open
-
[JENKINS-6659] Record a change message along with the job change history
Dave Hunt
added a comment - A simple textbox would be fine. Would also be great to have an option to make it a mandatory field.
Dave Hunt
added a comment - A simple textbox would be fine. Would also be great to have an option to make it a mandatory field. 
David Riley
added a comment - Also would like this, it would save a lot of time when trying to recall why a change was made. e.g. Why did I switch this job to run against version x instead of y?
Preferred UI would be a "reason" box at the end of the config (above save/apply) and then ability to add/modify from the job configuration history page.
Probably unrelated, but can the "Diff" column be moved to the far left or date to the right? When trying to find a change its painful to have to count down each time rather than being able to associate the previously selected diff with the date on the left.
David Riley
added a comment - Also would like this, it would save a lot of time when trying to recall why a change was made. e.g. Why did I switch this job to run against version x instead of y?
Preferred UI would be a "reason" box at the end of the config (above save/apply) and then ability to add/modify from the job configuration history page.
Probably unrelated, but can the "Diff" column be moved to the far left or date to the right? When trying to find a change its painful to have to count down each time rather than being able to associate the previously selected diff with the date on the left. 
Max Wahler
added a comment - Great idea! Sometimes, there are lots of changes to a job and if you want to revert something, you have to go through many diffs.
I'd also love a setting to make the change reason mandatory for specific jobs!
Max Wahler
added a comment - Great idea! Sometimes, there are lots of changes to a job and if you want to revert something, you have to go through many diffs.
I'd also love a setting to make the change reason mandatory for specific jobs! 
Gabriel Rositto
added a comment - It would be nice if this could be picked up even though it is old. It's a very useful feature for understanding config changes easier and it should be a relatively small effor.
Gabriel Rositto
added a comment - It would be nice if this could be picked up even though it is old. It's a very useful feature for understanding config changes easier and it should be a relatively small effor. I'm currently working on this and the recent idea would be a sticky textbox next to the configure page (see picture). 
"Really mandatory" fields are not possible as far as I know, since the user may just ignore the red errors/ warnings and click S_ave_ nonetheless.
It is possible to display an error/ warning depending on jch plugin configuration or to just always display it.
So what would be the preferred UI for this? A textbox at the end of the job/jenkins configuration pages?