JamieA Expert

I meant what version of the plugin. But ok so you are using an old version of the plugin. As I say this is fixed in recent versions but requires jira 6. No intention to backport my changes to previous versions.

What version? This is fixed in recent versions.

"WAS" only supports a few functions, membersOf is not one of them - see https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-functions-reference-764478342.html#Advancedsearching-functionsreference-membersOfmembersOf() Actually I don't see that what I said above is relevant, although obviously membersOf…

Probably some kind of jira bug. As you see in the work log tab all the entries are there. I've seen similar bugs where it barfs if there is not at least a one second difference in the creation time. In this case though I tested that and it still didn't work. Maybe for some reasons it assumes that they're all the same entry.

"be" is in the list of *stop words* in English, ie words that are not indexed so can't be searched for, because they are deemed to be too common. Unfortunately the list is hard-wired: http://www.koders.com/java/fid5FBD7DCAFB544D74598A9B1D82A341CD648DA47F.aspx?s=java#L1 The workaround IIRC is to change the indexing…

Should work fine but the more modern approach is to use IssueService to do an issue update. Also, the code above is for JIRA 6. On JIRA 7, remove the ".getDirectoryUser()"

You can try https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-CopyCustomFieldValues - it has a limited set of pairs of field types for copying. I can't remember if you can go from select to text... looks like not, but might be possible to go from single to multi, then multi to text, or you…

that's the same as my example...

'Database' in cfValues['Affected Area']*.value

There is a built-in task for the script runner plugin already.

Try reading Nicholas Muldoon's post here...http://www.nicholasmuldoon.com/2013/06/using-the-epic-workflow-in-greenhopper/ For a first step, you can get the stories of unresolved epics with: issueFunction in linkedIssuesOf("issuetype = Epic and resolution is empty", "is epic of") (linkedIssuesOf docs).

Yes for example "fire event when", the condition would be something like: issue.statusObject.name == 'Resolved' && ['user1', 'user2'].contains(issue.assigneeId) (untested). Then you add a new event to the notification scheme, this event gets fired by this post-function or listener. Very minimal amount of code to write.

You could try the "expression" function as it's a bit more flexible. But I think neither work with script fields. There are outstanding issues for this - perhaps https://productsupport.adaptavist.com/browse/SRJIRA-1907

the script runner will work with 4.4. Some of the built-in scripts will not yet work with 4.4, but that doesn't matter if you're providing your own.

As Radu suggested, your script would just be: issue.reporterId = issue.projectObject.leadUserName Providing this is the first post-function that should be sufficient.

The API may have changed since that answer. As Aleks said, the useful part of the error you get is in the "...". 

What information are you trying to get? Whatever it is it would be probably be easier to use the OSWorkflow api. eg: com.opensymphony.workflow.loader.WorkflowDescriptor#getSteps

related question: https://answers.atlassian.com/questions/12956/jira-full-ldap-integration-how-do-you-deal-with-retiring-users

Have a look at https://docs.atlassian.com/jira/6.4.3/com/atlassian/jira/issue/comments/CommentManager.html. You would iterate the comments on the source issue, and create corresponding comments on the target issue.

Typically this is what reports and gadgets are for as Nic said. However this was the use case for the aggregateExpression JQL function in Script Runner. If there are multiple different users in your filter you should get a data table with a value for the sum of the values by user. If you get the function params right...

The service name is anything you like, use it for your own info. The class is com.onresolve.jira.groovy.GroovyService. In the next part of the form you enter the path to the file... testService.groovy in your case.

Instead of sending an email can't you have the workflow step just create issue in the correct project... I know you're trying to avoid plugins which is fair enough, but this is not possible without plugins. Eg https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Clonesanissueandlinks

This is what you want: http://docs.atlassian.com/fisheye-crucible/latest/wadl/crucible.html#d2e607

Actually Crucible+Fisheye are paired, they cannot be installed separately. Moreover, if you are using subversion (and I assume you are because there are better review/insight tools for git), it should be co-hosted with the subversion server, or at least the repos be accessible via the file:// scheme.

You should probably be looking at the Conditions, not the Validators. However I don't believe there is any plugin available in OnDemand that has this functionality.

Yes.

There's nothing in here relating to a transition. But I'd sort out:Script field failed on issue: PYF-98, field: Scripted answer 1ie fix the script field, and removing the field from the other plugin, then it might be clearer what is going on.

The way you describe it it sounds like a browser issue - can you hit F12 and look for errors, also check the atlassian-jira.log file on the server for problems.

Not at all. I'll take a look tomorrow.

What browser are you using?