Comments
-
Have you changed the version of java? That could be a cause of VerifyError... but I don't think the error above is the root cause error.
-
Possibly the same issue as https://studio.plugins.atlassian.com/browse/GRV-56 but without seeing the logs it's difficult to say. Unfortunately the reporter of GRV-56 never got back to me so I don't know if the suggestion to up the XX:ReservedCodeCacheSize worked.
-
Well maybe you could tag your question correctly then you will get better targeted responses.
-
You can fire a custom event in a listener if the filed changes - see https://jamieechlin.atlassian.net/wiki/display/GRV/Built-in%20Scripts#Built-InScripts-Firesaneventwhenconditionistrue You then hook that event to a velocity template if you want to use velocity. If you don't want to use velocity you can write your own…
-
What exactly do you mean by "block in db"? What is different when you run it in Script Console, is it the issue that you are copying? What DMBS are you using?
-
projectMgr.getProjectObjByKey("CREOSD2").Id is wrong, should be projectMgr.getProjectObjByKey("CREOSD2").id You may have other problems but you should at least start with something that will compile.
-
The most recent release has better and more concise error messages for script field failures.
-
It needs to have better error messages than that, I'll look into it.
-
As Alexey said, it looks like the problem is that a user has been renamed. What version of the plugin are you using?
-
I'm not exactly sure what you are trying to do but in the other answer, 'return "null"' is almost certainly not what you want. Instead just: return null Regarding proper syntax for is null - generally you just want to use groovy truth, and not distinguish between nulls and empty strings. So I would just use: if (!…
-
it's saying 10151 does not exist. Can you paste here the url of the dashboard
-
But you are not using a 1.5 version!
-
It's a plugins 1 plugin... read the docs. You need to use the old school method of copying both jars to web-inf/lib
-
Problem with dashboard distro plugin is I think it read it shares absolutely everything, which is not what everyone wants.
-
The plugin betsy is referring to is the script runner. To share with everyone you share with "jira-users" or whatever group(s) you have given the USE permission to.
-
> The issue assignee is NOT the reporter AND is NOT "Unassigned". have you tried: issue.assignee && issue.assignee != originalIssue.reporter
-
In that case it depends whether you need what it does. The slowness, unless you've written it really badly, is just because creating issues is comparatively slow. If you write it as a java plugin, it will be just as slow, but take 10 times longer to write.
-
This has been covered quite a lot before... things like workflow functions won't have a systemic effect on your instance. If you don't notice it doing the transition, then you don't have a problem. Recent versions of the plugin record timing and logs: https://scriptrunner.adaptavist.com/latest/jira/#_logging_and_profiling.…
-
And the version of the script runner plugin?
-
What version of jira and the plugin? Works fine for me.
-
Works fine, you just can't nest double-quotes like that. Using single quotes for the inner query. issueFunction in subtasksOf("issueFunction in parentsOf('assignee = currentUser()')")
-
You need ChangeHistoryManager to get at previous values.
-
there is a lot of sample code for getting custom field values... you need CustomFieldManager, then issue.getCustomFieldValue(customfield)
-
Memes are good, but if you tag the question correctly with the plugin's tag, you will get more attention! originalIssue.getCustomFieldValue(customfield) will work in a validator only. For post-functions, it depends on the ordering of the functions, if your function comes before "store and reindex" you can retrieve the…
-
If anyone has this required in a hosted env there is now an easier solution than in the old forum post - use this built-in script to fire an event when the field has whatever value, or changes to that value, or send a completely custom email.
-
yes, the title in the docs is not the same as in the product... our fault.
-
I think you know what Steven meant, and we've given you the best answers we have at the moment.
-
I think from speaking to various people that it's pretty clear that we are missing some basic tutorials, for people with no prior knowledge. And we'll work on that. Most people I think get started by adapting examples found either here, or on https://scriptrunner.adaptavist.com/latest/. But maybe other people have better…
-
jquery dollar has been "noConflict"ed to AJS.$, so instead use: AJS.$(function () { // page load...})
-
I created an issue for this: https://productsupport.adaptavist.com/browse/SRJIRA-2018