Fabio Racobaldo [Catworkx] Community Champion

Hi Connor, here your code : import java.util.Collection; import com.atlassian.jira.issue.Issue; Issue issue = issue; Collection<Issue> subTasks = issue.getSubTaskObjects(); int count = 0; for(Issue is : subTasks){ if(!is.getStatus().getName().equalsIgnoreCase("YOUR_STATUS_NAME_HERE")) count++; } return count; Hope this…

just voted

Hi Jeevan, you need to check the searcher associated to your field. Probably it is not selected. In order to that, you need to perform the following steps : * Go to the custom field list and locate your own scripted field * Click edit on the right * Select a Search Template (I suggest Free Text Searcher) It shoud fix your…

Hi Alessandro, there're many causes that could cause this issue. Please, check the following article in order to perform a first check : * https://confluence.atlassian.com/kb/health-check-lucene-index-files-location-873918046.html * https://confluence.atlassian.com/jirakb/jira-applications-performance-tuning-229179856.html…

Hi Andy, please could you provide us more information about your issue? Please, attach here catalina.out log file (form INST_JIRA/log folder). You talk about permission denied so I assume that user that you use to start service has not grants to operate on JIRA INST and HOME folder. Try to run this command before starting…

Please, click here 

You're welcome Jeff. Please mark the answer as accepted. Ciao, Fabio

Hi, It's true. Please read below If your Atlassian Cloud instance exceeds the storage limit, your instance will not be suspended, except in extreme circumstances, and we will not remove any data. If you exceed your storage limit by a small amount, and you're storing acceptable types of data, your applications will continue…

Hi Jeff, you need to search open issues and then go ahead as follow : * tools -> All XXX issues * Select issues at your convenience * Click next * Choose move issue and go ahead More information are available here https://confluence.atlassian.com/jira064/modifying-multiple-bulk-issues-720416468.html Hope this helps, Fabio

You're welcome Olivier. Please, mark this request as resolved accepting my answer. Ciao, Fabio

Please, could you try to change the following formats as follow ? jira.date.picker.java.format : dd/MM/yy jira.date.time.picker.java.format : dd/MM/yy Please, try to create a new issue and let me know if it fixes your issue. Ciao, Fabio

Please, could you provide me also the advanced configuration settings? Ciao, Fabio

Hi Olivier, which language is set as default in your system?

Hi Olivier, please check the configuration on System -> Look and Feel At the end of this page you will see the format that users will see on issues : Probably you are using default format dd/MMM/yy h:mm a and dd/MMM/yy. Please changes these two values into : dd/MM/yy h:mm a dd/MM/yy This shloud fix your issue. Ciao, Fabio

There are a lot of limitation using JIRA Cloud. You're welcome, Fabio

Hi Fulvio, sorry but on the cloud JIRA you can't add javascript to the announcement banner. You can not put in place this requirement. Ciao, Fabio

Hi Fulvio, if you try this code you can figure out that this approach works <script> alert("Script works"); </script> I had not chance to test your script Ciao, Fabio

Hi Alessandro, reviewing your configuration (that seems ok), I don't understand why SWROS-26 appears in the column "In Review" even if its status is "Waiting for Review" that should be mapped into "Waiting for Review" column. In my opinion there are some issues at index level. Please, perform the following steps : * System…

Hi Fulvio, did u test it?

Hi Fulvio, you can do that. You need just to add tag script within annoncement <script> jQuery().ready(function() { .... <YOUR CODE HERE> .... }); </script> Hope this helps, Fabio 

Hi ALessandro, please could you show me the column configuration?

Hi Cyrille, it's a known bug. Take a look here https://jira.atlassian.com/browse/JSWSERVER-15185 It has been fixed in 7.7.2, btw there was a regression in 7.8.1. Probably you are using a version with this bug. Ciao, Fabio

Hi Olivier, using script runner for JIRA, on add-on section you will find Behaviour Enter a new behaviour and map it with your project/issue type. Afetr doing that you can add a specific behaviour to your fields using the following documentation https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html Ciao,…

Hi Sarah, the provided code should retrieve information just about the space related to the page in with the macro is used. I just tested it to my environment and it works. Are you sure that you are using the correct one? 

Hi Birkir, as Jira Sys Admin, you should be able to access Admin->Application_>Jira Service Desk -> Email requests. There you can test your email addresses configuration and View an audit log for each specific address configured. This is the first step in order to understand what happened. At the following link you can…

Hi Olivier, in order to do that you need to use a custom script. A good solution is Script Runner for JIRA (https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/cloud/overview), in particular you could define a behaviour that, based on resolution selected, hide or not a specific field within…

Hi Shneior, at what level you need to get this information? At DB level, at application level? memberOf() is a JQL Function that allows you to filter something based on user mermebrship. For example, this query retrieve all issue whose assigne is a member of QA-HH group assignee in memberOf("QA-HH") If you need to retrieve…

Hi Sarah, you can define the following macro : ## Macro title: My Macro ## Macro has a body: Y or N ## Body processing: Selected body processing option ## Output: Selected output option ## ## Developed by: Fabio Racobaldo ## Date created: 28/03/2018 ## Installed by: Fabio Racobaldo ## @noparams #set($containerManagerClass…

Hi, you need to move all existing issues to another issue type before going ahead with issue type deletion. In order to do that you can move issue using bulk operation. Please, verify that all fields are present on your target issue type in order to not lose information during this operation. Using this approach you ca go…

Hi Prashant , probably you need to set commentField as not mandatory at the start of your code {code} import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.component.ComponentAccessor import com.onresolve.jira.groovy.user.FieldBehaviours import com.onresolve.jira.groovy.user.FormField ...…