JamieA Expert

Oh yeah, I keep being surprised about this new soap-rpc bridge, then forgetting about it, then getting surprised again. My bad.

Think you're muddling the soap and json rpc urls, but don't have the correct url to hand.

"comment" is not a regular field, and can't be used like that. I'm not really sure how to do what you're doing short of writing a custom script.

I had a quick look at the source and it's not configurable so far as I can tell. I would have suggested an Apache rewrite from /projects/PROJECT_KEY/repos/REPO_SLUG to "commits", but as you say the links in the repo list page are direct to "browse"... which is not very friendly. This should definitely be configurable, or…

Which field did you put that behaviour on? Versions please?

You can put compiled classes under there, but not uncompiled groovy classes. They need to go in a scripts directory.

They're not contradictory instructions... it should be under one of the script roots (typically <jira_home>/scripts), and then under the directory corresponding to its package. So an example for a post-function would be: <jira_home>/scripts/com/onresolve/scriptrunner/canned/jira/workflow/postfunctions

def ctx = new JiraServiceContextImpl(authenticationContext.getUser());def sr = searchRequestService.getFilter(ctx, results = def searchProvider.search(sr.getQuery(), authenticationContext.getUser(), PagerFilter.getUnlimitedFilter())def issues = results.getIssues();issues.each {issue-> /*DocumentIssueImpl*/ ... } I just…

Sounds like a bug. You could export the workflow as XML, edit the XML to remove this validator (just search for the classname), then create a new workflow based on this XML.

Thanks for letting me know. The widget on the custom field multiselect box was the main driver for this really. I will take a look at it again at some point because we're still feeling the pain points that it was intended for with jira 4.4. Unfortunately it's going to be quite fragile moving between versions, partly…

Blimey, was it that long ago... I just put it up at https://bitbucket.org/jamieechlin/jira-admin-prototype-extension. Let me know how you get on. I have not looked at it since then, and I think it was for jira 4.3. No guarantees, no refunds etc. Binary here.

Sounds like the users are not members of the group confluence-users. This could happen if you recently upgraded and something went screwy converting your ldap config to user directories. What version of confluence do you have?

What Nic said. You don't need to get the issue, you already have it.

Hrm... I agree about "most", but not about "almost all". IMHO it's useful to search for users commented by a particular user in a date range, or issues commented by say a troublesome customer. So I bothered to code for it ;-) To answer the original question, there's no performance hit if you use the comment index, both the…

"when something is marked as done it stores the local date on the users machine not the date on the server for that issue" That's not the case... it stores the server date but will display the date in the timezone of whoever is looking at it. At least that's since JIRA 4.4. If you want to get the user timezone, you will…

> Note that you seemingly need to pass a String containing the text 'true' or 'false', rather than a real boolean. Yes... this is what the browser would send, iirc. I forgot it doesn't have a no-arg ctor anymore so nice work sussing that out. Would be good if this was a bit more script-friendly.

"Unable to find component with key" This is annoying but expected, I have an unanswered question on this on this forum. Without seeing the logs I couldn't tell what is going wrong in your case.

When I need to do this I created a script for it... see below. Otherwise you could use wget/curl. in some loop of users... log.debug "Merge from $mergeFrom to $k" ScriptManager scriptManager = (ScriptManager) ComponentManager.getComponentInstanceOfType(ScriptManager.class); GroovyClassLoader gcl =…

No worries but... curious to know why it doesn't work without that as you're passing a user object to the relevant methods.

What happens when run as a service, just no issues retrieved? Or transition fails? Some methods check the current logged in user, just for kicks put this in and see if that works: ComponentAccessor.getJiraAuthenticationContext().setLoggedInUser(user)

I think this is a know problem with the version of axis in old jira versions - see https://jira.atlassian.com/browse/JRA-11693 and the linked issues.

The links will be that of the base url, defined in Admin -> General Config -> Base URL. You can only set one.

I'd try setting the following in your <home>/jira-config.properties file: jira.ajax.autocomplete.userpicker.limit = 100000 It should not come into play because you only have a few active users, but it's worth doing to rule it out.BTW just because you don't see a query, don't necessarily mean it's not running, the list of…

Can you paste a screenshot of how this is configured. Also check the names of the two fields, they must be typed exactly as they are displayed in the screen.

cfValues["Picker A"].containsAll(cfValues["Picker B"]) will be true if the values in A are a superset of those in B. That's for a "simple scripted condition", for a longhand script get the custom field values and use containsAll as above. note: will throw exception if called on an issue that does not have both these CFs…

Weird... can you do select * from customfield where cfname = 'issueFunction' and check the customfieldtypekey - it should be 'com.onresolve.jira.groovy.groovyrunner:jqlFunctionsCustomFieldType'. Is it?

OK, that makes sense.

Well, the logs are the first thing to check really.

Can you check the logs... the most important thing is that the condition for all the fast-track transitions are mutually exclusive. If it didn't work, either the condition didn't match, the transition wasn't applicable, or the transition failed - the last two of those will log something.

They are nothing to worry about... there is probably a bug report about the warnings, but I can't find it atm.