JamieA Expert

That macro hasn't worked for a couple of weeks...

You can get the connection through other means, eg https://studio.plugins.atlassian.com/wiki/display/GRV/Miscellaneous+Groovy+Scripts#MiscellaneousGroovyScripts-ExecuteaSQLquery

Use: if (componentField.getValue*.name.contains("Cameras")) (untested) getFormValues will return a list of component IDs, so your condition will never be true. > I turned logging on but dont see anything in th log window when I use F12 on the browser. It logs to atlassian-jira.log. But you should add some logging to your…

Definitely getting slower. Must be all those duplicated questions...

Did you check the logs?

First of all you're getting "customer", then later "Customer". It should be throwing an NPE with your code, check the logs.

Your println statements have gone to a different log... can you change the println to log.warn, and look for that output in the log.

You can just add some log.warn() statements. You will add the logging statements to your code, rather than turn logging on from some other package.

Add some logging so you can see what exactly is null... could be one of the custom fields for instance/

What context is this... some kind of post-function? What happens if the user has entered a description, do you want to just overwrite it?

That's not quite the case... no values are available in an initialiser whether set or not. You can get the value of any CF using the regular java api, getUnderlyingIssue() will give you the regular Issue object, then use issue.getCustomFieldValue

If following the support link from https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner it should add the plugin's tag. Maybe it was accidentally removed. The latest released version is compatible with 6.2, for why it's not marked as compatible…

If I remember correctly

I think it will not be OK.... IIRC it won't compile with that version of the API, so I would expect problems if you try it. But in a dev instance, it can't do much harm to try.

You should be able to do that with scriptrunner JQL functions - JIRA Agile examples here: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-MoreComplexExamples

No problem. Feel free to mark my answer as correct, to help other people.

svnkit is a java implementation of svn, as such it only needs to go on the server. It's not an svn client, except maybe for fanatical java types. It's used for solely for fisheye querying subversion repositories, or jira, if you use the jira-svn integration.

It's true that some custom field types are provided by plugins, which should be easy to identify. But some plugins will just create custom fields of standard types if not present, and there is no link back to the plugin. Eg gantt chart plugin.

You can't. What's the field name? The gantt chart plugin adds a bunch of global custom fields.

What version of the plugin are you using? Class reloading required a small change to groovy itself. In certain versions of my plugin I inadvertently shipped the vanilla groovy runtime. If you open the plugin jar with winrar or similar, in meta-inf/lib (I think) you should see a groovy-all-1.8.5-scriptrunner.jar. If it…

No, but you can buy a $10 licence.

Log in to my.atlassian.com, select your licence, then follow the "download source" link.

Yes, could you mark this as answered then.

Could you please see https://studio.plugins.atlassian.com/browse/GRV-56.

You cannot, but you certainly should be able to given that when Stash creates a branch it contains the issue key. Having to mention the issue in every commit is completely redundant. I think Atlassian are aware this is a problem, last I heard (a long time ago) they were investigating better methods of associating the issue…

Hi Christian, In general happy enough to speak to anyone but it would be pretty brief, my spare time is going into groovy jql functions at the moment. The mappings and behaviours are just properties so shd be easy to get out. Importing would involve mapping custom field ID to name, which is not so easy. Same problem with a…

Christian, I'm really sorry, there is nothing I can do today or tomorrow. Maybe next week time allowing. But what about jira 5.1 and above... what are your plans for that?

Also I think "AJS.$(document).bind('dialogContentReady'," should be changed to the NEW_CONTENT_ADDED event...

I would guess something is not getting cleared the second time the script is activated. There are one or two global variables (eg "behaviours" iirc) , I would try to clear them just inside the dialogContentReady block.

This should be fixed in the latest release.