JamieA Expert

You can't do that with ondemand. It's pretty trivial with the hosted version. AFAIK, you can't even inject javascript to do it that way. Your only other option is some program that uses the remote API which polls for unassigned issues every 5 mins or so, and assigns them based on that field value.

Also see https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-subtasksOf%28Subquery%29 And insert mandatory reference to JQL Tricks.

Multiple initialisers was in a recent release, 4.1.2, and the equivalent version for JIRA 6.x

Most likely some reference to an external system... ? You can use a regular expression validator, you can do this with Script Runner or there are plugins that offer this in a more targeted way.

Well, it will be the intersection of the result sets not the union because you used AND not OR, but I know what you mean. > is that an indexed lookup of some sort that would make it somewhat efficient since there is not project qualifier for the versionMatch function? I wouldn't anticipate that to be slow in any way…

> there was a problem with the import that's why i thought it didn't look like python.

Did you write that yourself, or copy it from somewhere? That doesn't even look like jython code.

Even if it's on the the screen it should default to the current user. Perhaps the O/P means the assignee...?

I get the mechanics of it, and that they probably want to validate the query before giving you a chance to save, but the job of their UI designers is to hide all that from the users and just make it work like magic.

There is something whacky about the UI around searches to be honest. If I open one of my filters, then make a simple change such as change the project clause. I want to save it but I only see the Save As button. Then I run the filter, and it changes to a Save button. This is a bit weird, that the behaviour should change…

In future can you use the "code" formatting from the toolbar, otherwise the code is more or less unreadable.

For viewing/printing (not editing) you could try https://studio.plugins.atlassian.com/wiki/display/JVIZ/JIRA+Workflow+Visualization+Plugin. I think graphviz produces much better layouts especially for complicated workflows. Disclosure... my plugin.

the problem is the "additional code" section runs before the issue is actually created. You could try putting Vasily's code in a "doAfterCreate" closure, eg: doAfterCreate { // add label} it may work.

As Robert said - but you could try https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-SetIssueSecurity . It just requires setting a simple condition which will determine when the security level changes. For your case you could actually just leave the condition blank and add it to the two…

Marketplace should bump the compatibility for minor releases, but for some reason it didn't and the compatibility only went to 6.4.8. I've changed that now so you should be able to find it in UPM, but if you can't, the way to do it as as Matheus mentioned. Can you upload from the marketplace download url directly.

No... I haven't really looked at JSD properly. Seems like they're assuming with JSD that all end-users are too stupid to understand a validation failure message. You can create a ticket (without service desk) at https://jamieechlin.atlassian.net/browse/GRVand I will look into it.

You just need a "simple scripted validator"... issue.dueDate >= new Date() + 5 That will show a red message on the ticket when they try to submit. (Nic - I ignored the popup window aspect... I don't think this needs to be client-side at all).

That sounds like a pretty good workaround.

ScriptRunner does not offer "edit validators"... you might try this: http://www.j-tricks.com/tutorials/one-fixversion-please (I have not personally tried it so can't vouch for whether it works with the latest version).

np, glad it worked out.

Hi... > Are the script runner functions only accessible via the administration -> Script Runner console? Are they available via the main search console in JIRA for end users They are JQL functions accessible to all users. > commented (by = jones) It should be this: issueFunction in commented('by jbloggs') Note the quotes.…

you need to add some logging... it looks OK, but it should either create the link or throw an error.

Doesn't sound like a scripted field... they are just used for derived values and are read-only. I think you just want a short text field, and do the linking in a post-function. But why don't you use the put the issue links system field on the screen? You can do that in recent versions...

not working how? check logs.

Guess this is an ondemand question based on the urls...

It will only work with a hard-coded summary. If you don't have that you will need to write your own script to reopen the subtask... which will have to include knowing which subtask to reopen, if more than one.

The subtask action can't be blank - it needs to know which transition to do on it. I guess the script title is not the most accurate. What it means to say, is that it will optionally do some action on the child, maybe because you want to keep it in sync with the parent state, for instance reopen it. Blank means you are…

If you install script runner plugin, you could run the clear jira caches script: https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-ClearJIRAorGroovyCaches If restarting makes it work, then probably this script will make it work too, without having to restart. Having said that, I agree…

If you install the plugin mentioned you can make use of the create subtask built-in script, so could be done without coding. However you get more control if you write a script as Byron has done, plus it's more fun.

IE conditional comments work fine in the announcement banner, eg: <!--[if IE 8]><div style="background-color: #FFFF00; padding: 2px; text-align: center; color: black;"> <strong>IE8</strong> - I wouldn't let my dog use IE8, get a better browser.</div><![endif]-->