Comments
-
Adaptavist have found a way to do this. I'm hoping to find out how.
-
Buehler?
-
Romina The SLA restarts at 0 each time it enters the "Waiting for Customer" status.
-
That's exactly how we are doing it. No problems so far!
-
Did that get you what you needed?
-
Yes! We are currently doing this by manipulating SLA's. We have a couple of automation tasks that allow this to take place. The first being that any time we make a comment to the customer, it moves the ticket through the workflow into a status called "Waiting for Customer" I believe this is a canned automation script. We…
-
Changing our request security back to "Entering a new participant's email address (this prevents customers from seeing the names and emails of other users)" instead of "Searching for existing users, or entering a new participant's email address" allowed us to use the delimiter, but does not validate that the users have an…
-
You cannot add groups as participants through the customer portal GUI. Only users or email addresses are valid options. We also do not want this to occur automatically, b/c the users should not be added until HR has completed a series of actions on their side, and they do not have SD licenses to advance workflow. We also…
-
If you are trying to switch between issue types with different workflows, you will need to use the "move" feature so it transitions the issue into the new workflow.
-
Update, known issue here: https://jira.atlassian.com/browse/JRA-63694
-
Thank you so much!
-
The answer depends on which version of ServiceDesk you are running. On the current version, the SLA's will be updated/recalculated automatically. On older versions, you will need to click the "update" or "recalculate" link under the SLA menu on the left. This will take a minute, and refresh all SLA's within your project.
-
Interesting note as well, if you buy a licence for Service Desk 3, you can download and install the previous version as an Add-On if you are still running JIRA core 6. The license works for both.
-
When you create an issue "manually", I am assuming that you are using the big blue "Create" button at the top of your screen. Creating in this fashion does not add a "Request Type", so the notifications will use your JIRA core notification scheme, and not the "Service Desk" scheme that it sounds like you are expecting. If…
-
Absolutely. If you download a previous version, you can simply install it as an add-on and your license for SD 3 will work. This is exactly how we are running in our organization. Previous versions of SD can be found at https://marketplace.atlassian.com/plugins/com.atlassian.servicedesk/versions We are running 2.5.9 on…
-
Service desk agents are counted by being a member of the "service-desk-agents" JIRA group. This is what provides access to perform actions as an agent in any project that has SD enbabled, such as workflow actions and internal comments. If a user has this license, they can work on multiple service desks, however a person…
-
Forgot the link to the ticket : https://jira.atlassian.com/browse/JSD-1809
-
You can do this either with a post function on create, or using the automator plugin. You will need to know the raw values for each of your request types from the database. This ticket has some info and instructions using the plugin, however the concepts are the same as a post function in workflow. Feel free to reply if…
-
Romina, I actually just responded to you on this questions as well. Thomas is correct that the timer is reset. https://answers.atlassian.com/questions/32967673
-
You could create an automation task of "when issue is created" trigger "make comment" This will however impact any "Time to first response" SLA's you may have configured.
-
We actually have this same issue. The box to select your time period as shown in the official Atlassian Documentation here: https://confluence.atlassian.com/servicedeskserver032/collecting-customer-satisfaction-csat-feedback-828800786.html Simply does not exists. Can we get some attention to this?
-
We would like this as well. In fact, the ability to use this feature inside of the standard "Create" button on all JIRA screens would be even better, as we could then use our URL ticket creation script to invite customers.
-
I have 7.3 Data Center and cannot see the Labs option anywhere. I need this in order to enable boards for my business projects.
-
Notification helper assumed JIRA Core notification scheme, which is super-ceded by JSD's scheme if a Request Type is present on the issue. If you want those members to be immediately notified of all new issues created, you could achieve this through a workflow post function - but it might be easier to create a filter…
-
Different scenario. Mine is working as expected for a default config, but I'm wanting to modify the config
-
Another option would be to have SD create my users in the Delegated Authority User Directory like the base JIRA create user option does.
-
Can something like this be implemented within Service Desk? The queues are already there, I just want to limit how many can assigned to each user at a time.
-
Admin's would be defined the same way as JIRA core. Either in an admin group or specifying users for the Admin role within your Service Desk project. Either way, we have 4 admins in ours.
-
Solved it! Below is the proper syntax in case any one else has any of these issues: !issue.get("customfield_15480").getName().equals(issue.get("reporter").getName())