![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
07/Jul/13 8:16 PM
|
|
Description:
|
Renaming jobs
- can cause wrong behavior in some plugins (job-specific permissions in Role Strategy due to design or favorites in Favorites plugin due to brokenness come to mind)
- can be an expensive operation when many relationships between jobs are affected (upstream/downstream relations, trigger parameterized buildplugin, copy artifacts plugin, ...)
- breaks bookmarks and links in documentation (external wiki, or even view descriptions) and notification emails
All of these are possible reasons that administrators might want to prevent users from renaming jobs while still allowing them to configure.
Job names are also mostly unrelated to a job's content, i.e. there's usually little relation between the scripts or programs a job calls (and the act of configuring this) and how the job is named in Jenkins.
Therefore the new permission Job/Rename (or Item/Rename) should be introduced, and renaming items should require that permission instead of Configure.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Daniel Beck
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
