Support option to change default priority in WRM 5.0
This was requested by . The Jira team plans to defer all the scripts by default (to check the perf benefits) and adding this option will reduce their manual labor. We will benefit here since Jira is willing to test the WRM 5 alpha release in the process (if we deliver this feature sooner).
Users should be able to change default priority via API or system property. We could create sth. similar to WebResourceIntegration.getDefaultPriority, see https://stash.atlassian.com/projects/JIRASERVER/repos/jira/compare/diff?sourceBranch=refs%2Fheads%2Fissue%2FNONE-spike-script-deferred&targetRepoId=5713
It’s possible that changing default priority will break RefApp.
How to test?
RefApp demo should work as expected
if default priority is hardcoded, integration tests have to be updated