|
||||||||||||||
|
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 |
||||||||||||||
|
||||||||||||||
|
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 |
||||||||||||||
When the source project is using a variable, it is not known at the time the configuration is saved (when you use a particular project, we can check if that project is accessible to the person saving the configuration). Thus, we have to do some permission check when the job is run. I chose a simple solution that requires fairly open permissions, but at least makes the permissions clear. A pseudo-user as you suggest could work, but care would need to be taken to ensure the security implications of granting permissions to this user are made clear. Another solution that would work just for the multi-configuration case would be to detect when the variable is only used for selecting a particular configuration, but the project itself is fixed.. thus a permission check against that project could be done when the configuration is saved.