We have been using Jira for a number of years for our own software tools and one off custom projects.
We already have a full blown ticketing system for support, we need an intermediate tool while are custom software is still unreleased and being tested by the client.
I have installed service desk on-top of our Jira, customers can enter issues, bugs etc through the portal. I have two Application Engineers that are agents in service desk. They validate the issues and then I want them to but the bug into our normal jira.
I have a number of dev teams that can work on these issues, but they are not agents. How to they collaborate on a service desk project.
Can I link a service desk project to a jira project? Struggling with the concept. We don't want to have our dev as agents.
90% of these service desk tickets will be bugs and or feature request, not support. Once the customer as signed off and the systems are in production then they will end up with our normal IT support system.
@Dean Holmes, this a a question that has been posed many times and there are answers out there but takes some digging. I will provide a quick summary of how I and many folks deal w/ this.
In this way you keep your developers in JSW and customer support/IT agents in JSD. You can setup your developers as collaborators for the JSD project so they can comment internally and browse issues.
controls cost as you don't have (want) developers to be agents.
hope this helps.
I have JSD 3.4.2 and no longer available COLLABORATORS option, how resolv "comment internally and browse issues." for my developers?
I find that is possible without need licenese for developers in Jira Service Desk:
https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-users-732528877.html?_ga=2.30950396.218880159.1548859681-717687986.1548256179 - section Involve Jira Software or Jira Core users
But I have not succeeded.
I did all the setting from links above but the developers from Jira Software don't see the Project and Issues from Jira Service Desk only if I give access in Aplication access to JIRA Service Desk but this action leads to exceeding maximum allowed license in Jira Service Desk
that is absolutely the issue. one instance does not know about the other. I have never connected two instances so I'm not sure I can provide direct assistance. there are some threads about connecting two instances. I would recommend using the search box at the top of the page. FWIW, i think two instances creates unnecessary complexity.
@Jack Brickey this is a useful thread, thank you.
What relationship should the (new duplicate) JSW and JSD issue have so that the requester can view the status of the JSW issue, while retaining the "Waiting for Agent/Customer" statuses in the JSD issue? The user story I believe looks like this:
The clean answer is perhaps that the user can see the status of a linked issue, but that linked issue is (I think?) in the JSW so the requester should not have access. Thank you in advance for any clarity.
I think I'm in the right place but not able to find my answer.
Today our users/business sign-in to jira service desk to create tickets/support and for being able to see the entire list of tickets they have created.
Once created, we (product team) review them (first line support) in order to prioritize them to add them in the sprint of our jira software. However, if we just move it from service desk to software then users cannot see their tickets anymore in jira service desk. So we duplicate the issue in software but it is not efficient and a waste of time. Also, once the ticket is done, we have to look for the ticket in service desk and inform business (again a waste of time).
How it is supposed to work?
Thank you in advance,
@sgroazil , this thread speaks precisely to your question. You don’t move the original issue to the JSW project as it breaks the connection with the customer. Rather you create a linked issue and if desired add automation such that the JSD issue is updated based upon the transitions of the JSW issue. Yes you end up with two tickets for on issue but the benefits outweigh the singular inconvenience.
If you are on cloud you can use “create linked issue”. Here is an article - create-a-linked-issue-to-collaborate-with-other-jira-product . By using this you can easily see the link in the issue allowing you to navigate between the two.
as Far as the automation it depends on your exact goals..
Hi @Dean Holmeswhere you able to find any documentation on how to link JSD Issues to JSW Project?
I want to do the same thing. I have a team of 3 JSD Agents, and I want them to be able to Link their JSD issues to JSW. So my development team can solve the bugs or requests.
Have anyone of you where able to to that configuration?
I haven't find any documentation.
Hi @Dean Holmes,
It sounds like you may have solved your most immediate needs, but just in case this is helpful for you, my company makes the Backbone Issue Sync app which you might want to check out. https://marketplace.atlassian.com/plugins/com.k15t.backbone.backbone-issue-sync/server/overview
One of our primary use cases are synchronizing tickets across instances that are set up to provide multiple layers of support (or to triage support tickets with development teams). Here is one such scenario explained: https://www.k15t.com/blog/2017/01/keeping-1st-level-and-2nd-level-it-support-teams-in-sync
We think our app takes some of the pain out of such processes. Hope this is of help! Cheers,
we are struggling with the same issue. We don't want to clone/duplicate every ticket that is assigned to the development team. The 2 tickets always are out of sync and yes there are nice plugins that can sync that for you. But we just simply want 1 ticket for the whole process and it's fine that only the support employees can communicate with the customer through the portal.
My main question is; can I use the same workflow that I use in the Jira software for devs for a issue type of a service desk project? thank you for an answer!
Thank you, yes I also tested it.
But doesn't solve my problem of a normal simpel flow that a customer requests something, dev makes it and customer can monitor it through the portal. Devs don't have to talk directly to customer. But you really don't want to have 2 tickets in your system for the same issue/request/bug or what ever. Every solution (sync add ons etc) are not a real solution, just a work around for a problem that should not be a problem because technical its possible.
I understand your need, however we wanted to keep them separate. We’ve been using Jira for a very long time and have all our internal project and engineering team integrated into our Jira workflows.
We added service desk for user acceptance testing (UAT) a place for clients to raise questions, freature request, bugs, training etc. We needed different workflows for that. An agent can triage a ticket and determine if the issue is a bug or the user requires training. They can request more information,screen grabs etc. If it is a bug or FR then with a couple of clicks it can raise either feature request or bug issues in Jira for engineering. Again depending on feature request or bug they have different workflows.
I did get the two system talking, so that when a relevant step in Jira is made it updates the steps in service desk. So far we are very please, in fact I Demoed to our board yesterday, I’m now task to see if it can replace our own in house support ticketing system.
the expensive proposition is to make them agents.
Depending on what you mean "collaborating" exactly - you may want to look into the Servicedesk automation.
Here you can for example update a service desk ticket when a linked ticket (like a dev ticket) changes.
Also for more advanced stuff there is a automation for Jira App in the Marketplace which is very feature rich:
We are a marketplace developer and use the combination of the above to automate our support and work with linked tickets.
Thanks, this all seems very painful and expensive for a simple problem.
We simply need clients to be able to report issues, we then validate and put them dev for bug fixes. We have a custom workflow in Jira that works.
We just need the client limited visibility, service desk works but dev should not have to be agents, we should be able to have agents assign an issue to a dev. They should be able to update the workflow when bug fixes is done and the customer have visibility to the status.
The only communication between the client should be agents
Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events