Laurens Coppens Expert

Hi, You can only choose users that have customer/user permissions on that JSD project. This is due to security/privacy reasons. You can try to add the managers to the "Customers" Role on the JSD project, then they should be listed in the user picker. Regards, Laurens

John, Clicking the pencil should do the trick, if not you could try another browser, old IE versions or compatibility mode sometimes block stuff like this. Regards, Laurens

Eddy, There is some migration documentation but thats mostly when you want to move your userbase to crowd, without the LDAP link. If the usernames in jira matches the usernames in LDAP than you can try to import the memberships and then switch over to LDAP. If not i think your in for some manual work. You can always try to…

Jeff, Here is some good documentation about how to setup approvals: https://confluence.atlassian.com/servicedeskcloud/setting-up-approvals-816880004.html Basically you choose a user or group custom field to use for the approval process in your workflow and then you can use that field as a hidden field in the customer…

Gonclaves, Magic, i didn't know you could filter like that. Just tried it and works like a charm!

See answer Goncalves! 

Jamil, Apologies for the very late reply but i think that it will just not work like that. My guess is you will just have to get used to the standard share button. Regards, Laurens

Chris, Some wild guesses: Customer notifications are on a project level, so could it be that you only changed one project and the notification is coming from another project? Also the notifications can be set per language, so maybe you only changed english and the support team their jira user language is set to something…

Nicola, You will need an add-on like JSU to perform custom field updates in workflow post functions. Jira out of the box doesn't support the update of custom fields, only basic fields. Regards, Laurens

Michaela, You will need to contact your confluence administrator in order to get access to those documents. Regards, Laurens

Cindy, If you set a condition in an automation rule, it will only trigger the action when it is met. Instead of the assign action in the screenshot you can choose to run a transition

@Jamil Rahimov Not sure but chances are that the customers don't have browse user permissions: https://confluence.atlassian.com/adminjiraserver070/managing-global-permissions-749382914.html

What is the reason that you don't want to do this through the share button?

Post functions are executed after the transition is triggered, they can never trigger a transition. You can find some more info on advanced workflows here: https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html

Cindy, You just need to set an automation rule on your project (or a global rule) Just type GG and look for "automation rules" and you will be directed to the automation configuration. A post function will not work if you just want to transition when you check the checkbox since checking the box isn't a workflow action.…

@Jamil Rahimov I don't understand why you want to do that, but since you got the "actions plugin" you should be able to define a new action "add people" which shows the "request participants" field and does a transition.

If you are edditing an existing workflow it is automatically applied when you save it. So you don't need to add it to the project as it is already assigned to the project and issue type.

@Cloud_NEW Automation is a plugin: https://marketplace.atlassian.com/apps/1211836/automation-lite-for-jira?hosting=server&tab=overview There is a Lite (free) version and a pro (paid) version. I think the Lite version is able to check field changes. Once installed you can create an automation rule, select as trigger the…

@Cloud_NEW I would do this with automation for jira, when the checkbox custom field changes => check content and if all is checked => transition issue

@Senthilkumar You will have to be a bit more specific. You can find workflow editing options here: https://confluence.atlassian.com/adminjiracloud/editing-an-issue-workflow-844500771.html

@Mate Major I'm afraid the answer is no, the influencing of kb is limited to labels and content of the article. https://confluence.atlassian.com/servicedeskserver035/serving-customers-with-a-knowledge-base-894759682.html

@Tom Not sure how i did it then, but now you can just add an automation rule with the automation plugin and add it like that. I still use this script to add it to all projects but automation is a bit more user friendly :)

If public signup is enabled (as described here: https://confluence.atlassian.com/servicedeskcloud/set-up-customer-permissions-732528940.html - Can customers create their own accounts? = Yes) then customers who email the service desk should get an account as stated in the docs: * If anyone can email your service desk, then…

Przemek, I think the most valuable points are 1,2,4,5,7,8 and use case A is most common i think. Insight discovery only applies to people who purchase that, so i wouldn't include it in the general trainings. Same for the add-ons like SCCM. I would cover the import CSV and import LDAP part as these are used in most insight…

Ruby, I think the only way this will work is through a scriptrunner script. Out of the box automation rules do not have any capability to check the users language as far as i know. You can however add a language custom field to your request and use an automation rule on that custom field. Less scripting but it requires…

Nico, Have you enabled public signup? This is needed for your setup to work. For more info you can check: https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html Regards, Laurens

Hi @[deleted] This is not supported with referenced fields, you can't reference a referenced field. I had a similar setup: Insight field (field1) referenced insight field (field2) insight field with issue scope like this: (objecttype = "yourobjecttype" and "attribute field1" = ${field1} and "attribute field2"= ${field2})…

Raymond, The best way to do this is through a third party plugin like Refined: https://marketplace.atlassian.com/apps/1218481/refined-sites-for-jira-service-desk This gives you the ability to customise your help center with extra navigation. Hope this helps, Laurens

If you use the html-macro you should be able to use the following extensions: servicedesk/customer/user/requests?reporter=all&status=open&portalId=1&requestTypeId=17&page=1 portalid is your service desk portal requestTypeId specifies the request type

Koti, There is a plugin for this: https://marketplace.atlassian.com/apps/1218030/exalate-hp-alm-jira-integration?hosting=cloud&tab=overview Regards, Laurens