JamieA Expert

It should work but unless you can provide more information than "it doesn't work", ie log output, you are not going to get much help. But personally, I would not fire up a 3.13 instance to try to debug this myself.

Yes... you would just use this post-function twice with different conditions, and firing different events.

I think this is not the plugin you are looking for... in your other instance you can click through on the validator, in the URL IIRC it has the class of the validator. I don;t think it comes from SR. Easy to write though with Simple Scripted Validator from SR.

Must be a plugin or someone's hacked the source. You can try importing the backup xml into a pristine jira 3.13 instance and see if that works.

That exception doesn't seem relevant, no. I would reindex and take it from there, that at least will give you the right direction to look. "NULL VALUE BEING RETURNED ALL THE WAY ALONG" is not in the jira 3.13 source code as far as I can tell, so maybe check what plugins you have.

This is not particularly easy so I'll give a full example. First, add a Raw XML Module to create the web section in the Projects dropdown: <web-section key='recent-proj-cat-projects' name='ScriptRunner generated web item - active-issues' location='browse_link' weight='70'> <label>Recent CAT1 Projects</label> <param…

This should be very similar to the provided examples, except you want to get the project history and filter on the category. Something like: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.user.UserProjectHistoryManagerdef historyManager =…

Yeah it's fine... the ID used in a param to a SR function will refer to the ID of an action in the current workflow, unless otherwise made clear.

Only if the issue to which it's attached is accessible by the group "Anyone" - check the browse issue permission in your perm schemes for the relevant project.

ok I updated my answer

What you want is to have the validation run when the Version object is created though, no? There's not much point in not letting people pick an existing fix version... Which is more tricky. Something like this: import com.atlassian.jira.issue.Issueimport com.opensymphony.workflow.InvalidInputExceptionIssue issue = issuedef…

Kevin - could you ask a new question with a bit more detail... I have lost the context here. thanks.

Calculated fields are not really suitable for values which use "now" as an input, they will only get indexed when the issue is changed, so you can't usefully query on them. I think this is discussed here... https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted%20Fields- there are also examples similar to what you're…

You can do it like this: def rendererManager = ComponentAccessor.getComponent(RendererManager.class) def fieldLayoutItem = ComponentAccessor.getFieldLayoutManager().getFieldLayout(issue).getFieldLayoutItem("comment") def renderer = rendererManager.getRendererForField(fieldLayoutItem) renderer.render(issue.description,…

As Nic said. In this case the difference in numbers of modules is partly due to behaviours, but mostly because JQL functions are now their own modules so they can be individually disabled. The script fields should be fine... but see Nic's more complete answer.

Not possible I think because the user custom fields list is only showing those fields that are UserCFType or MultiUserCFType. So unless the participants field were to extend MultiUserCFType, which it does not atm, then it won't show it.

thanks 

> What you're suggesting is to search directly on the server or? Yes I was, but OK I understand now. Tibor's script is fine, although I would prob just write it as : issue.attachments*.filesize.sum() Make sure you set a Number searcher so you can find issues with a large total attachment size.

What context are you trying to use that script in? It appears to be a workflow function...? Can you not just do this with unix find and use the attachment store on disk?

Confluence is very weak at displaying source code imho. For years I've been using a wordpress plugin where you specify a url in your <pre> tag and it pulls the code from the url, which is usually a subversion url. I completely agree about pasting in code, so, if you create an RFE, I'll vote for it.

Nope... I guess you didn't follow your upgrade procedure!

This class: com.onresolve.jira.groovy.GroovyRunner - does not exist in 3.0.5, or 3.0.6. It must be getting it from somewhere. Check <home>/plugins/installed-plugins, if all else fails delete <home>/plugins/.osgi-plugins and restart. You could try uninstalling and reinstalled 3.0.5, but you should get the same problem.

The stack trace refers to classes that don't even exist in the plugin anymore. Are you sure you don't have a very old version in WEB-INF/lib ? Also check "Manage Addons", that there is only one version listed.

Not the same code but similar.

Can't you use a calculated custom field? If it's the case that the value is calculated but then can be overridden by the user, then use the behaviours plugin. Otherwise, a calulated custom field is the better option. Script runner plugin has "scripted fields", should you wish to use groovy.

Exactly what Christian said. If you don't need to use the behaviours plugin and you can do everything server-side, then do it. Use behaviours when you want dynamic form behaviour, or you want the user to be able to override the suggestion.

Yes - the first format just returns whether skip screen check is set. 

You mean the name of the source repo, assuming these are cross-repository pull requests?Also you should probably remove the "jira" tag and add a "stash" one.

Is this really related to JIRA Agile?

yeah that's what i meant