|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
To @domi’s example, I would argue that if you are disabling automatic archiving for a job then probably you are making other detailed changes to the job and might as well keep this section expanded. But this is a clearly a matter of taste.
Changing the appearance of the Advanced button when customizations are present should be easy enough if that is the consensus UI. (Probably a bit easier than the current patch, actually, since you could make such a change retroactively after invoking the body, so there is no need for the j:mute hack.)
Any thoughts on the actual appearance? Colorizing it in e.g. red would be easy enough, though it is not very accessible. Boldfacing the label would not show up well with all fonts. Adding an asterisk * may work but is not particularly discoverable; perhaps there is some broadly recognized Unicode character or icon that could be used to indicate that a field has edits. Glowing animation could be used but is again not accessible and could be seen as intrusive.
The current code captures internal field names, not display labels, so the actual list of customized fields probably cannot be displayed. (Some controls provide a reliable way to get an associated display label, but others I think do not.)