If IT developers and technicians are defined as collaborators, then how can we measure their input in SLA when we cannot assign an issue to a collaborator?
How do you suggest we measure 2nd level support in our SLA reports?
Seems like a step backwards if the only solution is to start cloning issues and having to track multiple versions of an issue just due to whomever is working on it. Kinda removes one of the keystones of JIRA functionality which is the ability to have all info in one place for a particular issue or item.
I disagree - you still have everything placed in one place - in Jira (since SD is just a "plugin" on top of Jira engine). The only difference is the fact that you get it bit more "puzzled" by putting some additional project separation (instead of having 1 project you have 1 for SD and 1 for 2nd+ level). Of course if collaborator could be tracked by SLA directly in SD it would be in favor, but since it is NOT available, then I am providing a potential solution that does not require to enlist every single developer/2nd level support as Agent.
Since Service Desk issues are based on predefined SLAs, field "due date" is no longer applicable at customer portal level. Is there a way to propagate the SLA(time to resolution) value to the cloned JIRA issue (such as due date field) so that 2nd level support have an indication on issue resolution deadline?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG