Ivan Tovbin Expert

Ahh, true.

I suppose the safest way is to create a support zip and hit Atlassian Support with it.

Issue voting perhaps?

What do the logs say?

Assuming 'myFieldValue' is a string then I guess you've ran into a known issue with static type checking in ScriptRunner not always being accurate. More info here. With that in mind I would simply ignore this error and see if the actual validator works.

The reason why your custom field is still displayed even if it's seemingly empty is as follows: Like I said, the expected value of a 'Version picker' type field is an array of 'version objects'. It means that the field will always have a value - an array, regardless of that array itself being empty or not. For your field…

Assuming the id of your 'Environment found in' field is '11111' the code should look something like this: import com.atlassian.jira.component.ComponentAccessor def cf = ComponentAccessor.getCustomFieldManager().getCustomFieldObject(11111.toLong()) String cfValueString = issue.getCustomFieldValue(cf).toString() return…

Hi Dan, The solution here is to create a scripted custom field which would be populated automatically with the value or values from other fields. I might be able to assist further if you could provide a more detailed description of your use case. Specifically the type of your source custom field (my money's on a multi-line…

Take a look at startOfDay(), endOfDay(), starOfWeek(), endOfWeek() etc. JQL functions. They provide at least some degree of dynamic date change in your filters. More info here.

Check you atlassian-jira-log file for the stack trace of that error. If all else fails I'd contact Atlassian Support.

Hi Ilya, I think you came across a known JSD bug, which prevents service desk type projects from being created if the default language is set to Russian. Check this ticket for more details. The workaround is to change you default language to English, create a project, and then change it back to Russian. It's rather…

Fortunately I've got JWT installed in my test instance, so I've had the chance to test it myself and it does work just fine. That said I can see a couple of possible reasons as to why it doesn't work for you: 1) The 'Current user' doesn't have the permission to execute the transition you wanna use in your post function. 2)…

Hi John, I think this is definately possible, not out of the box however. The kind of automation you described will require the use of 3rd party addons to implement. Please check this thread for a quick run down on the most popular addons. Given the potential amount of conditions I'd personally go with scripting as it…

Hi Tim, As you probably know, a custom field is always hidden from issue view unless it has a value set. There's a an open feature request here regarding this very behaviour. Since you are using a 'Version Picker' template for your custom field, the expected value for this field is an array of 'version' objects, that's why…

Try setting this post function AFTER the "Re-index an issue to keep indexes in sync with the database." post function.

Have you tried changing the searcher to 'Free text searcher'? Or that somehow goes against your process logic?

Ah, I got a bit confused. So the question is how to search for issues with an empty custom field which has its searcher set to 'Issue Key Searcher'.

issuetype = Feature and "Feature Link" is not empty

That's because 'Feature' is an issue type and not the name of the field, at least judging by your description. A correct JQL would look something like this: issuetype = Feature and <custom field name> is not empty

Hi Peter, The first link is simply a list of ALL portals (service desk type projects) across your JSD instance. The second one is a specific portal of a specific project. And that's also the reason why only this link contains your Confluence link. Connection to Confluence space is configured on a per project basis. The…

Hi Morgan, The best way to do this, is to add this user (or group) to a project role. After that grant that project role proper permissions within your project. Also please note that by default Jira already has some project roles configured and all new projects come with a default permission scheme which grants different…

Howdy! I'd start with this documentation.

Hi Lindsay, You might wanna accept your own answer to mark this ticket as 'Solved' Cheers.

Issues recieve a green checkmark when they recieve a resolution . Status has nothing to do with it. So the reason why your issues don't have a green checkmark is most likely because their 'Resolution' field have no value set (displayed as 'Unresolved')

Well then if the search is run AFTER the quarter has ended then I think this should work: created >= startOfMonth(-3) and created <= endOfMonth(-1) and resolution is empty

I think you should try something like: created >= startOfMonth(-3) and resolution is empty

Right, let's get this show on the road, shall we? Try this: import com.atlassian.jira.component.ComponentAccessor def attMgr = ComponentAccessor.getAttachmentManager() def attachments = attMgr.getAttachments(issue) def parentAttachments = attMgr.getAttachments(issue.getParentObject()) def lastAtt = attachments[0] def…

No problem, let's add a file size check, to be extra safe. Sure, it's not 100% bulletproof, but I have a feeling that a scenario where a file will have an EXACT size of the original after the edits is VERY unlikely.

Hi Germain, I think a slightly different approach will help you solve this. What if you just modify the script that is used to copy an attachment from a sub-task to its parent so that if there's already an attachment in the parent issue with the EXACT SAME name then the attachment from the sub-task will not be copied?…

Check out this documentation to learn more about static type checking in Scriptrunner. Thing is, static type checking in ScriptRunner is not always accurate and thus can be ignored at times. In this very case you can pretty much ignore this error, it'll work just fine as is.