JamieA Expert

You need the com.atlassian.jira.issue.util.AggregateTimeTrackingBean IIRC... I have done this before but can't find sample code. Probably best to look at the jira source.

Correct. It's not that I want you to, but it will give you better error messages. But look at your script fields as Nic said. If you only have one then that's the culprit and you need to check the code.

You should upgrade to the latest, it will give you a better error message: https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0#Upgradingto3.0-MarketplaceCompatibility-isitcompatiblewithJIRA6.2?

What version of Script Runner are you using? Later versions have much better logging when there is a problem.

Yeah this happens with script runner... it doesn't have any functional effect, but yeah it is annoying. There are bugs for it in jamieechlin.atlassian.net/wiki/display/GRV/.

With a simple scripted validator: (! cfValues["Select List"].value?.startsWith("Yes")) || cfValues["Other Field"] (untested - if it doesn't work break it down and do it piece by piece in the condition tester). Can also be done with a behaviour which will show the user that the field is required before they click submit,…

> If a ticket is created during the day During the day where, on the server? Or from the perspective of the reporter, or from the person viewing the query? You probably want it from the perspective of the people actually responsible from support, who may all be in the same timezone as the server... afaik you would need to…

The equivalent of the jelly script can also be implemented using a program that use the jira remote API, ie a program you would write then schedule to run every 20 minutes or whatever. I doubt Jelly will ever be enabled because it lets you do absolutely anything, if you know how.

Can you provide the log messages.

I updated my answer with my reasoning...

Write a jira gadget: https://developer.atlassian.com/display/GADGETS/Packaging+your+Gadget+as+an+Atlassian+Plugin. Once written you can add it to any confluence page. I would not use sql to access the jira database from confluence, although that's also possible... Update: The reason why not is because if you write a…

You can normally send url parameter: decorator=none ... but there is not enough context here to be sure.

This has already been asked, but the search is so bad I can't find it, and google doesn't seem to like a.a.c. Anyway, short answer is set the Group Object Filter to something that won't get anything, eg: (objectCategory=GroupsDisabled)

Yes... write your own javascript hooks, or behaviours plugin, or (I believe it's called) Live Fields in JJUPIN. And a few other plugins. For rolling your own javascript, there are lots of questions about that here.

Something like: status = Open and not status changed after -2w

It won't, not without polling the db, which you don't want to do.

I think the better solution would be to stop manipulating the db directly, and change your external process to use jira's soap or rest APIs. But the script runner has a built-in script to reindex issues either from a project or a query, you could use that or look at the code. Alternatively write a service that compares the…

I think you can... you can remove components from the available selection so you should be able to do that based on issue type.

This is the closest example. The second part explains how to create an Option, which is what you need by the sounds of things: https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/select-list-other.html

What's the point of this? You will just end up with a long list of options for the cascading field that contains the Cartesian product of both single selects options.

i'm familiar with groovy scripted fields: https://studio.plugins.atlassian.com/wiki/display/GRV/Scripted+Fields#ScriptedFields-Calculateanumberbasedonotherfields

OK... sorry, not familiar with that plugin.

You are using some plugin, but which one? What language is that?

change the DEBUG to WARN and rerun.

Can you set the log level to debug: https://scriptrunner.adaptavist.com/latest/jira/getting-help.html#_support_requests - then doing the failing transition, then post the whole log. If it's private you can create a ticket at https://productsupport.adaptavist.com/servicedesk/customer/portal/2

After the log message you posted there should be a stack trace - is there not one? Is HREO-15 the parent issue? Can you attach a screenshot of the configuration of the workflow function.

great, thanks for letting me know.

Plugin version? Recent versions of the plugin should tell you exactly which field is causing the problem.

Are you using jira 6.1? The data from that column has been removed, see https://developer.atlassian.com/display/JIRADEV/Preparing+for+JIRA+6.1#PreparingforJIRA6.1-editprojectkeydb (Nothing to do with postgres).

Cool... sounds like you want a post-function on the transition rather than a listener then. And thanks ;-)