Fabio Racobaldo [Catworkx] Community Champion

Hi @kedar , there are some specific function to filter dates within JIRA. Here some examples. Hope this helps,Ciao, Fabio

Hi @Ricky M , using built-in feature you can't do that. I had the same issue and I fixed using https://marketplace.atlassian.com/apps/23216/field-security-plugin-for-jira?hosting=server&tab=overview . Using this plugin you can hide specific fields to specific users, moreover the related tab will be hide. Hope this helps,…

Hi Stefano, please read the following guide https://confluence.atlassian.com/kb/how-to-import-a-public-ssl-certificate-into-a-jvm-867025849.html Let me know if you have problem with that. Ciao, Fabio

Hi, did u imported certificate into the cacert' Are u using a reverse proxy?

Hi @Stefano Sbalchiero, did u try to import cert into jdk cacert? https://confluence.atlassian.com/kb/how-to-import-a-public-ssl-certificate-into-a-jvm-867025849.html Please could you provide JIRA_INST/conf/server.xml configuration? Ciao, Fabio

If he is not the reporter he can't see the request. In order to see a request, he should be added as partecipant https://confluence.atlassian.com/servicedeskcloud/adding-request-participants-732528959.html Ciao, Fabio

It could, but this is an investigation. I haven't visibility about your project configuration, business requirements and so on.

On cloud you can't do that. Please, check user permission in order to figure out if he can see the other 6 ticket missing on the portal. Check if "reporter" has "Browse project" permission on the related permission scheme associated to you project. Fabio

Hi Peter, are you on cloud or on premise instance? 

Hi @Saad, disabling comments for reporter is not a correct way. Reporter can not comment tickets anymore and its reply should not create a new ticket.

Hi @Johannes, you can disable a specific shortcut (for the whole Confluence and not per space basis) using the following approach : * Go to the admin console * Select Add-ons * Select 'System' * Search for the 'Confluence Keyboard Shortcuts Plugin' and expand it * Click on 'Manage plugin modules' to see the individual…

I'm available. Ciao, Fabio

Non-customer comments In previous versions of JIRA Service Desk, when a person who was not already a customer or participant on a request replied to an email related to an existing request within that service desk, that reply would create a new request. This could be confusing for both the customer and the agents involved…

Hi @Raphael R., prefix should not be the problem. If the subject contains an existing issue key, email should be added as comment. 

Hi @Manish Sewlikar, try using the following approach : project = XXX AND ("Defect ID" ~647 OR "Defect ID" ~333 OR "Defect ID" ~ 444) Hope this helps. Ciao, Fabio 

Hi @Saad, by default JSD incoming email uses subject to identify if the email should be associated to an existing ticket or not (issue key in subject). You could try to disable that JSD email and try to use "Incoming mail handler" provided by JIRA Core. You can choose one of the provided handler Here a complete how to…

Please debug your code in order to figure out if user has a value

You need to persist the change : import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.issue.MutableIssue; import com.atlassian.jira.user.ApplicationUser; import com.atlassian.jira.issue.fields.CustomField; import com.atlassian.jira.issue.Issue; import com.atlassian.jira.issue.IssueManager;…

Hi @Bhavana, try using JIRA Command Line Interface (CLI) It has addVersion action. You run it directly, script it, or use csv with runFromCsv. Ciao, Fabio

strange, it should work. Try using directly issue (delete line "Issue issue = getUnderlyingIssue();" from previous script. Let me know, Ciao, Fabio

Issue issue = getUnderlyingIssue(); this method is provided by ScriptRunner. Are u using this plugin or is it something custom? In the second option you need to retrieve the issue key based on the context. Ciao, Fabio 

got it! issue object is null. Try this : import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.issue.MutableIssue; import com.atlassian.jira.user.ApplicationUser; import com.atlassian.jira.issue.fields.CustomField; import com.atlassian.jira.issue.Issue; Issue issue = getUnderlyingIssue();…

try using \n fro the carriage return. Please, accept my answer! Ciao, Fabio

Are you sure hthat CustomFIeld name is correct? try this : import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.issue.MutableIssue; import com.atlassian.jira.user.ApplicationUser; import com.atlassian.jira.issue.fields.CustomField; MutableIssue issue =…

Hi @Antonio D_Errico, the problem should be related to getCustomFIeldValue that should return a generic value and not a ApplicationUser. Please, try this code : import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.issue.MutableIssue; import com.atlassian.jira.user.ApplicationUser; import…

Hi Peter, Project Reindexing Permission Scheme Check if customer respect browse issue permission in the related permission scheme associated to the project

Hi @Kevin Paulus, when the trial expires, all plugin functionality will stop working. All PostFunction, Conditions, Validator will remain in your workflows so you need to manually delete from them. This could have impact to your business. Ciao, Fabio

Hi Peter, please could you try to perform a reindex at project level? Moreover, could you check the permission scheme in order to figure out if user has capability to see those 6 tickets? Ciao, Fabio

You're welcome. Please, mark my answer as accepted

;) Please, mark my answer as accepted