JamieA Expert

yes. cfValues is indexed only by *name*.

I don't really see what the problem is... if you don't want to hard-code the name you need to hard-code the ID. Personally I prefer name because it's portable between instances. In your case you need to get multiple fields by multiple IDs.

Look up the CF by ID... def customFieldManager = ComponentAccessor.getCustomFieldManager()def cf = customFieldManager.getCustomFieldObject(12345)return issue.getCustomFieldValue(cf)?.value == "True"

There is a workflow condition which requires that a review exist. I don't use studio but it's part of the fisheye-jira plugin so I imagine it will be in studio. I believe there is also a post-function that will create a review. Have a look at what workflow functions are available to you.

Fisheye/Crucible is never going to be fast unless you only have a toy repo indexed. But for comparison we have 500Gb of index data... performance is OK after it received a lot of admin love recently, which mainly comprised identifying all the bad "svn copies" (of branches and tags) and automatically adding exclusion rules…

Isn't it as simple as removing their Schedule Issue permissions?

Do you mean a future version of the plugin? If so you are able to do that now... maybe I'm missing something, or perhaps your answer doesn't relate to the question?

You have to write code to do it rather than choose options from the web UI. You would use: getActionName() == "Create" && <your code to see if the current user is in group X>

I would copy them to a formatted table in the description. But... you should do this, it will make your instance faster, more maintainable and easy to use.

The resolution field is intrinsically related to your workflow, so it doesn't make any sense to put it on an edit screen. All of your states should either map to resolved (possibly a specific resolution) or to unresolved. If that's the case you should only put it on a transition, or unset it using a post-function, from…

Did you try "previous status" built-in script?

Sounds like the js could do with some profiling. That being the case I'd take a look at the excel to table options, that way you don't need to edit the page at all.

I don't think 1500 is that great a number. I'd double invert the question by asking what's the maximum number of rows a user can handle in Excel? 1500 doesn't seem like a lot. It depends on your browser... if you've having problems you're probably using IE. Maybe you could use the excel to table macro... there are also a…

Some sort of service to run every few mins to synchronise the groups I guess. There is no "user added to group" event afaik that you could listen for.

You must have ScriptRunner Robert so you should just be able to replace the validator with the one provided by Thanos, rather than using whatever function JMWE is providing.

When you say "number of codes" - what do you mean - the issue key?

Will try to reproduce... but looks quite involved.

What type of field is Request Participants? You can see that in Admin -> Custom Fields. May be a multi user picker?

I don't think this is a ScriptRunner issue. I don't know what plugin provides that field, but it looks like they've (sensibly) decided to escape the HTML, to avoid XSRF attacks. You could use a regular text field and set the renderer to wiki markup, then write the link using JIRA wiki markup.

The ID is unique but not the name. If you want to query by component ID alone you wouldn't need to join on project.

> People usually recommend Script Runner because it allows you to essentially write plugins, without having to package up and install a pluginPeople do recommend it for that reason but in this case it would be useful because of the powerful built-in JQL functions it provides...…

We use it with 1400 repositories, a jira repo is automatically created for any new svn repo. In short, it works fine for us, the svn index is only 40-60Mb or something. However I changed the plugin substantially... Retrieving the propertysets was extremely slow on oracle so I made lots of optimisations there. The main…

If you can enable the html macro you might be able to do it all through css and js eg http://odyniec.net/projects/imgareaselect/ Pretty sexy jquery plugin...

in a transition, the current comment is in: transientVars["comment"] - so if that's empty no comment was added

get the comments in the same way as above but using "issue", not sourceIssue.

If you are using the "clones issue" built-in post-function, you can enter the following code into the additional issue actions: import com.atlassian.jira.component.ComponentAccessordef commentManager = ComponentAccessor.getCommentManager()def comments = commentManager.getComments(sourceIssue)if (comments) {…

No, it's not single-threaded. Quite possible disable and enabling fixed it, that fixes quite a lot of things.

I don't like that answer! If you get a chance could you try going back to .14, see if it still doesn't work. You can always go back to .12.

Can you attach a screenshot?

I'm shocked and appalled. 3.0.14 hasn't been out for "weeks" so you must have upgraded the plugin... from which version?