JamieA Expert

If the resolution shows "unresolved" as one of the options, you have a problem. Someone must have created a resolution called "unresolved"...? Mass confusion normally ensues after this.

I don't understand why you upgraded to such an old version... it's extremely hard to imagine what might be the problem with a version that's 2.5 years old. But please have a look what's in your log file.

Did Atlassian not tell you that jira 5.1 is out of support? Are there any errors in your log file?

Behaviours wasn't merged into Script Runner until 3.0, so you will still need both, as you are on a very old version of jira. If you use the latest compatible version of both you should be fine.

We will... we won't be keeping it to ourselves!

Can you confirm you have the hosted version not the cloud version? If a restart does not fix it please create a support ticket at https://productsupport.adaptavist.com/servicedesk/customer/portal/2

If you are using a paid-for version please create a ticket at https://productsupport.adaptavist.com/servicedesk/customer/portal/2

Nope, that should be fine.

Cool. For some of the functions you will need to perform a background reindex... but not that one.

You need to install a recent version of the script runner plugin... is that plugin present?

Can you try 0.5.3? There are a lot of changes between .5.0 and .5.3.

Download it from somewhere that does have internet access, transfer it to your workstation, then do "Install Plugin -> From file" (or something similar).

Put your function first in the list, it should work then. 

Cool... is there anything you can share to help other people in a similar predicament?

I don't know why it used to work, but it makes sense to me that it doesn't work now. Conditions can only return true or false, so the MWE condition will just return false for the current user. If the condition returns false then it's not available to fast-track. I don't know what version of SR you upgraded from, perhaps…

There should also be a catalina.out file in there somewhere... (do a find). If the jvm is crashing it will dump the stack trace to that file. Also there is a jvm argument to make it dump core on crash that you could add, if you're familiar withgdb that could help. > or at least it drops off the "top" process list I'm not…

Oh hrm i'm not sure what version of ScriptRunner you have. You could try epicsOf("issuetype = Task") instead of linkedIssuesOf.

Doesn't work how? Can you find one issue that does appear and should not, or does not appear and should, and describe it? Ie issue type and links.

At it's simplest something like: issuetype = Epic and not issueFunction in linkedIssuesOf("issuetype = Task") but you probably would want to add additional filter clauses to the linkedIssuesOf function.

This is https://jamieechlin.atlassian.net/browse/GRV-250 - it's currently not possible but will be implemented in the near future.

The other issue is that the custom field name might have trailing white space...

Case is significant. Why don't you post the real name of the custom field, I doubt it is called customText.

Sounds like you've done the hard bit. You can retrieve and get custom field values using code like this. If you set this as the first post-function in your transition you shouldn't need to do much more than this. package examplesimport com.atlassian.jira.component.ComponentAccessorimport…

This is pretty similar to this question, but simpler. To find Bugs without subtasks: issueFunction not in hasSubtasks() and issuetype = Bug To find subtasks of Bugs: issueFunction in subtasksOf("issuetype = Bug") You can combine these to create: (issueFunction not in hasSubtasks() and issuetype = Bug) OR issueFunction in…

Feel free to create an issue. Like I say though, I do not currently plan to resurrect this functionality. Yes you should just be able to create an account on that cloud instance... if that doesn't work please can you contact Atlassian support, as they seem to keep reconfiguring it such that it's unusable.

Can't seem to add an answer. I've never seen that before, and I'm not really sure what you mean by "jira projects role list". This particular function has been removed from the recent releases... it was done before Atlassian introduced embedded crowd, and it needed a lot more work to make it work with Crowd.

Could be referring to using it for ordering... which imho is the only thing it can be used for in filters.

Hrm, if that's your need, then your way is the only of doing it AFAIK (as far as I know). I really don't think you can do this with jql, but maybe a jql expert will chime in.

You may be entering into the realms of having to create your own jira report.

You can't use the GH rank field for filtering AFAIK, just for sorting. The actual value will be a large, arbitrary number. Unfortunately there is no top(n) operator like you have in sql in jql, so I can't see how you can have a query that returns the top 3 ranked issues per department or something else. Also my…