Alexander Bondarev_x6gjf3 Expert

Hi, @Dirk Ronsmans I had the same question before - https://community.atlassian.com/t5/Jira-Core-questions/Scripted-field-where-we-can-see-the-JQL-filter-s-results/qaq-p/1018559

Hi, @Nik Weber Why do you want to use different projects to each Service-Desk`s Levels? We always use one project with different Security Levels(documentation - Configuring issue-level security), if you have a goal to hide information from different Support Levels - you can just change Security Level on issue transition`s…

Hi, @Tania Clarke Thank you for article! Very interesting and useful improvements! The ability to edit tasks directly from the queues is especially useful! This will actually shorten the processing time for requests. Do you have in plans to implement it in the server version?

JQL - it is just language to search in this case, it is not command line(( I think you should check project permitions, I seте you an article in first comment(change on cloud version).

JQL - it is just language to search in this case, it is not command line(( I think you should check project permitions, I seте you an article in first comment(change on cloud version).

Hi, @Leo As I know, out-of-box in JSD Automation you can`t change comment author, Try Automation for Jira - Cloud Lite or Automation for Jira if Lite version can`t do it in Cloud.

in practice, we don`t act according to such a scheme. just for this case, I suggested a solution. in fact, it does not matter, because we define on event, either of notify project roles or groups.

it doesn't matter, you can use any search

@Jack Brickey Like I told i firstly add user then make him customer. In your case you can set 'project-role'(JSD-Customers) notifications on new Event(#2).

Hi, @[deleted] Jira has 'Bulk-Change' for this case - Editing multiple issues at the same time

Then you can pick 'column' and add all fields that you need in. Then 'Export' 'CSV Current fields'

Hi, yes, it is possible, look through the Atlassian Documentation: Basic searching Advanced searching

@Jack Brickey , I checked it now again - Server 7.11.1. 1. Create new user with new group(Administration - User management) 2. Add customer by searching on new username

If you`ll get questions - please contact, I will try to help :)

interesting solution, but 'out-of-box'. I would advise you to study your notification scheme in advance. because if you have a lot of clients and they will constantly receive letters on their comments that a new task has been created / updated status - they will quickly start complaining. there is also the possibility that…

menno.jansma@proactis.com , i know how to resolve your problem. As I see the nice solution is creating a transition available to certain people(JSD-agents) in certan conditions that will send an email notification to a specific group. So you can create any custom Email to the group using plugins(for example - Jira Misc…

Confluence Server 6.10.0

Hi, @Geoff Wilson ! I did as you described, but checking under the Administrator test account - I still see the space and its pages. Magic?)

Hi, @Richard Saffell . It looks like you need in reindexing data. Look throught this useful article.

Problem with trigger("when"), "In-box" JSD doesn`t have "issue matches" in column "when", You can try Nicholas solutin with creating new SLA`s, but it may be too much SLA`s, So I can recommend you to try Automation for Jira - Server Lite, It is free, 

like i told - automation just make transition, which will create another issue.(there will be post-function to issue creation and linking(for example, ScriptRunner - look here)). you should create hidden transition from "completed" status to "completed" status=)

as for me, the easiest way is Scriptrunner - https://scriptrunner.adaptavist.com/5.4.47/jira/builtin-scripts.html#_copy_custom_field_values

It is classic - you can create custom rule in JSD Automation. But firstly you should create hidden from customers transition, which will create new linked issue, then "in-box" JSD Automation do what you need:

Yes, it is known problem : JSDSERVER-5655; JSDCLOUD-5600 Look throught this question and answers for it.

can you clarify the reasons?

To first trigger you can use Jira Service Desk in-box automation , issue matches - "Time to first response" <= 24h and send mail or anything else. For regular sending(in-box) - you can create cron scheduler on filter - "Time to first response" <= 24h Out of box - using pluging like Automation for Jira Automation Lite for…

if you describe your case in detail (which SLA is used, the principle of its calculation, the desired result) - I will try to help you with JQL request and automation configure,

Hi @Victor Lubuku Look through this article. Use can easily create any automations in JSD.

Sorry, i have not seen your answer when writing my reply. Yes, it works!

but i have found solution!! you should add any option on "Customer Request Type", then 'reporter' will see it on the portal.) So, we should add this field on creation screen and hide from portal screen.