JamieA Expert

Thanks for the tick, hopefully other people will chime him with more information. One final piece of advice - test it! And then again every 6 months or so.

Sounds unnecessarily complex... your JDBC url should contain the DNS alias for the database server, such that if the database is failed over then it the same url automatically points to the DR database system. Unless you are a very small company this should be provided for you by the DBAs I would have thought. I don't use…

Yes, your systems admin guys will be fired if they agreed to what you are suggesting anyway;-) Particularly ssh - if that was allowed we wouldn't have the fun of doing reverse tunnelling through socks proxies.

Your question was about access through the firewall to the public internet. Nearly none of those ports should be through the firewall, eg your SMTP server, database etc will all be inside the firewall.

Prevent the UPM from even attempting it with -Dupm.pac.disable=true.

Hrm... if you do a direct translation of your code to java you will have the same problem, IF the issue is in your code and not Script Runner as I suspect. If you fix it in java, you could apply the same fix to your script and the problem will go away.

At least one of those is your script field code, from the stack trace and if you are using an inline script, you cannot tell which one it is. I would consider moving that code to a file, then from the thread dump you can see which of your fields is misbehaving. It's probably worth doing a quick audit of your script…

Should work fine. The post-functions that run on Y are effectively independent of the ones that have run on X. Cloning may well Y to Z should also create the link X to Z, so you may want to manage that with the checkLink closure.

If you want to remove the STC error you can use: oDate as Date Problem is the type checker can only infer it's an Object.

Yes, basically you need to format it properly. It might be better to do it like this, if you have users with different language settings I think you may need to: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.datetime.DateTimeFormatterFactoryimport…

We have also seen links disappearing for no apparent reason. Sorry this doesn't help, just saying others are experiencing the same...

Jobin is right, that's the obvious thing. Check also that the role Developers has View Version Control permissions in the permission scheme, and that the current user is in jira-developers.

I think "due date" should be "duedate". At least log.warn the value of dueField, so you cna see if it's null. Any errors in the log?

<jira.home>/logs/atlassian-jira.log, typically.

It doesn't look obviously wrong, but depending on what version you're using maybe Contract_type is not what you think it is. Add log.warn (" Contract_type : ${Contract_type}") after you get the value of it, then refresh the page, and tail your logs to see the value.

If the field doesn't confirm to the standard ones then yes, it would need to be treated differently. One of the issues with this plugin is it needs to have specific knowledge of all the various field types.

It should work fine. You must have modified this script, are you sure you haven't introduced any changes that would break it? What version of jira and what version of the plugin?

You're welcome ;-)

Upvoted for clearly explaining the steps that you went through and including correctly formatted code!

No problem. You need to explicitly set both attributes. I was going to change the code so that setRequired would also ensure it was shown, but I don't think I ever did that. In recent versions you can chain calls. So a more succinct version of your code would be: FormField ExtractType = getFieldById…

You probably want this: FormField ExtractType = getFieldById ("customfield_10312")FormField ExtractName = getFieldById ("customfield_10313")String pulltype = (String) ExtractType.getValue()if (pulltype == "Data Extract") { ExtractName.setHidden(false)}else { ExtractName.setHidden(true) } The changes are: 1. the CF ID you…

Good comment... yeah, it wouldn't make much sense if they didn't ;-) I don't think there's any straightforward option then... shove it in sharepoint.

It's not possible AFAIK. If you have permission to view the issue it's attached to, you can view the attachment. You could create a sub-task and attach the file to that, then use issue security schemes to control access to the sub-task.

The broader question would be can you limit the amount of memory used by any particular plugin, and the answer is no, not to my knowledge. I wouldn't even know how you'd work out what memory was attributable to which plugin.

Check the logs - you can see how to up the log level here: https://jamieechlin.atlassian.net/wiki/display/GRV/getting%20help#GettingHelp-Supportrequests This will show you the condition that's being evaluated and what it returned. If you only want this to fire on In Progress, why don't you put it as a post-function on…

or you can create an issue at https://jamieechlin.atlassian.net/browse/GRV and get us a backup of your db if you're desperate.

we tried to reproduce this actually... can you try in a different workflow/project or something so we can rule things out?

The problem seems to be related to one of the select/multiselect/radio/checkbox fields on the parent issue, that is also on the child issue. Are there any like this?

That's the wrong dbconfig.xml... that one is for hsql.

Until I know where this issue originates it's difficult to track it down: https://answers.atlassian.com/questions/15290084/which-plugins-supplies-this-code . Do you have any non-standard atlassian labs plugins?