![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
plugin |
|
Created:
|
07/Aug/14 8:02 PM
|
|
Description:
|
It often occurs that I have to downgrade (and/or not upgrade) a certain plugin. It would be helpful if I could add a note as to why so myself (or a future admin) doesn't upgrade breaking changes.
Ideally such a note would be able to be applied to each plugin. But one single note section to the Plugin Manager update center would be sufficient.
(if it was for each plugin, it could show why and how first installed/last updated)
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
J Knurek
|
|
|
|
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/d/optout.
