Evaluating Jira Service Desk.
We send all support email from our individual business email accounts using our local email client apps. We don't want to change that.
So, how can I change JSD's rules so that I can manually change an issue's state from "Waiting for service" to "Waiting for customer" in the JSD dashboard after I replied to the customer with normal email?
In the current config it seems this transition can only happen by using JIRA to communicate with the customer. This is too enterprisey and mechanical for our style of support. We want instead to keep the personal touch. So we want a service desk that keeps track of our communications without taking them over.
@Raynard Rhodesanswer gave me the hint i needed to find the next step. thanks.
there's a whole mess of complexity available in designing your own workflows, issue types, workflow schemata, forms, displays, metrics, blah blah all that enterprisey stuff middle managers like. the trial for JSD is initially populated with a load of stuff that's useless to us. so we need to delete it all and start over with one issue type and one simple workflow. i managed to find how to create a new workflow but haven't had time to do it.
and that's the difficulty we have with jira, as with zendesk and presumably the others, is their intrinsic complexity. to make it work for us, i need to dedicate somebody's time to administration of jira. i have to invest in taming jira's baroque complexity before i can know if it even has the possibility to be useful to us.
our firm has only two full-time staff. we've spent hours on it already and only gotten started. it's really discouraging.
Here's an ISD. I replied to a customer's question by email, cc: support desk, asking the customer for more info.
The state WAITING FOR SUPPORT is wrong so I have to change it to WAITING FOR CUSTOMER. How do I do this?
The Workflow dropdown menu for changing the ISD's state does not allow this transition.
If I click the Respond to customer button then I get this form, the one I was talking about.
I hesitate to use it because I already responded to the customer by email and that's why I need to change the ISD state.
On the list of ISD's there's another dropdown menu like this
This suggests to me that the business logic for this service desk allows directly transitioning the ISD state to IN PROGRESS, ESCALATED, RESOLVED, CANCELED and PENDING but the only way to transition to WAITING FOR CUSTOMER (the only state that correctly represents the real world status) is by completing the Respond to customer action.
So the problem is not that state transitions trigger automatic notifications (which can be disabled). The problem is that I cannot transition except as a result of sending a message.
How can I resolve this? It seems I need to customize the business logic of this app.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event