JamieA Expert

It doesn't support renaming users across directories. Upgrade to the latest version of jira which should support this. I'm going to remove this function in the next release.

Seems to work for me so I'm marking it as compatible...

Not really. For one thing only project admins can create versions, but more people could potentially create issues. You could use some custom field and then a post-function that creates a version, but I'd strongly recommend against it. You wouldn't capture the release date and description, and people will typo in the wrong…

See http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Cloning - "Configuring the cloned issue summary field prefix" section.

I'm going to disagree with the other replies. My opinion is that that configuration is fine but it totally depends on the load and the capabilities of the machine. The biggest hog is Fisheye, depending on the size and "shape" of your repositories you may need a lot of memory, and as above, during indexing it will use as…

I can't really remember, but I think yes, just edit the workflow you are using to remove that condition or restrict it to the developers role. Have a look at "auto assign" as well - http://confluence.atlassian.com/display/GH/Configuring+your+General+Project+Settings.

AFAIK you need to remove the condition requiring that "current user == assignee" for the workflow.

You could be the first ever user of Script Runner for Confluence, which has facilities for copying page trees, including adjusting internal links within that tree.

I think this is a different problem, please ask a new question.

That's not javascript (js), that's groovy, as such it needs to have the extension .groovy. The exception shows you that the wrong interpreter is being invoked: sun.org.mozilla.javascript.internal.EvaluatorException If you have applied the updated workflow with the script post-function, there will be an exception in the…

IIRC: sum.setFormValue("") I missed the training course unfortunately 

If so change the last line to if (qavalue && devvalue) { sum.setFormValue(qavalue + devvalue)}else { sum.setFormValue(0)}

You don't need to return it but should not make a difference. Can you describe when it should be set to zero? Your question wasn't really clear, is that you want the sum to be zero if either field is zero?

For both of them can you not just do: def qavalue = qa.getValue() as Integer ?: 0 Then they will both non-null, and you can just add them and avoid the null-checking. Or use what Nic said but you do need the setFormValue.

try putting it last in the list, perhaps refreshing the issue from issueManager.

"INCOMPATIBLE - UPDATE REQUESTED" - you need to either download from marketplace and then upload, or click "add new plugin" and point to the marketplace url. The version you are using is not marked as compatible either, so you may as well update.

Could be a javascript issue then... can you update to the latest... 3.0.14? What browser are you using? (PS: don't upgrade if you are on IE8).

Is Issue Security the name of the scheme? That dropdown doesn't look correct, what version of the plugin and JIRA do you have? Can you attach a screenshot of the issue security levels admin page, for that scheme.

Jennifer: If you tag your question with script runner tag I am much more likely to respond. Justin: Script Runner has all the jql functionality that that plugin has, and is free. If you start by getting the second part right and saving it as a filter. Then use "in parentsOf("filter = 12345") ", that should work. It's hard…

sure

Yeah... this wouldn't matter so much of I could do a search on all new or updated questions with tags I follow since wednesday, but afaik I can't.

Well, it says browsers greater than Netscape 6 and IE 5.5, so it is valid. It does look a bit odd though I agree.

Did this used to be available? I didn't think I made it available because I never felt that it was finished. I'll have a look at adding it back for 3.0.7. https://jamieechlin.atlassian.net/browse/GRV-531

The documentation: https://tempoplugin.jira.com/wiki/display/TEMPO/Tempo+dynamic+drop-downs - last heading, implies it can send the issue key. In which case you should be able to get the url from the servletRequest: https://scriptrunner.adaptavist.com/latest/jira/rest-endpoints.html#_configuration Then look up the issue,…

No, because the DN for each of those users are not under the base DN for the directory.

If you only want to get users in certain groups, then create a user filter that only selects users in those groups (memberOf in active directory). Test on a dev instance...

Your base dn is ou=Groups, so it will get groups but not users. Make the base db higher, then you can set an additional group DN.

Sounds like your user filter or base may be incorrect.. can you check, or click "directory summary" and put that info here (anonymise if necessary).

You should, but it would be very nice if you could put conditions on the create step, as you can have much greater control with conditions than you get in the permission scheme.

Hrm... as a first step can you try disabling then enabling the plugin? If that doesn't work can you try restarting jira, if you haven't already.