Merging boards and projects is very confusing. I was able to create a board for whatever reason. I am not clear how it works now. I don't know where my support board is.
In my opinion, the problem with new UI is, that boards can no longer be associated to service desk projects. This was possible before.
We can now either associate the board to a profile or to a separate software project. Unfortunately, both don't fit, as a new project will have a new key and a personal board makes no sense, as it's not a personal board.
So to sum up, the new UI destroyed the possibility to have boards in service desk projects, which made multiple boards in our setup just disappear, and we don't know what we should do with them now. Our workflow is completely broken.
The articles mentioned don't adress this major issue either!
Could you please explain in detail how the service desk should play together now with software projects and agile boards?
Service Desk projects don't natively support boards like Software projects do. So it won't be visible on the side tab. However, you can still navigate to Boards (top bar) and you can find your board there.
What I would suggest is add a link to the kanban board under Project Shortcuts.
Take a look at the Knowledge base article Boards in the new Jira experience for a better understanding of the changes. There is also a parent article that has some links on the right discussing various parts of the new UI that you can find at Introducing your new Jira experience.
I got around this issue like this:
I'm confused as I don't have to do this in cloud. I can create a Kanban for JSD project simply by changing the location to be my profile. I think the issue is the board for a non-SW project can't be allocated to the project's location. Not really even sure what that capabilities that provides tbh. The board will work fine for my needs. BTW, I don't think this is a new UI issue but may maybe it does behave differently. I have switched back to the old and occasionally switch back to test some things.
you can create the Kanban board and save to your profile location as mentioned above. Regarding Esther's comment "....only in your profile..." you can add the board shortcut to the JSD project sidebar using the "add shortcut". This allows anyone to access from the JSD project page, of course you need to share the board. They can also favorite the board if desired.
I think what @Harold Wong is saying is that, if you're a team that currently only uses Service Desk, if you want to be able to use kanban boards, you also need to pay for Jira Software (a separate set of licenses which are cheaper than service desk agent licenses.)
This is true. And it still doesn't address the fact that most workarounds, like creating a board in a profile or another project isn't the ideal experience. There's another more recent (but less active) post that I answered in more detail.
I do understand the reasoning behind not having boards; Service Desk is designed for teams who work in a triage flow, handling issues as they come in. But the fact that you can customize a service desk project's workflow does suggest that you should also be able to change the view of how your teams work.
I'm a huge advocate of Service Desk, but it does have limitations.
We have a mixed environment, yes it is true some teams, especially IT do not use boards but our PM and upper management do. I assumed moving up in licenses (I consider service desk license and upgrade from software, and software an upgrade from core) would retain all previous features and unlock more features.
In my Org we have started moving all depts to JIRA so that we can interconnect especially with new hires and offboarding. With service desk with can set SLAs on the different workflows. But if this will remove their kanban boards then I see it as a problem as we need to purchase additional licenses just to give them that one feature. Service desk licenses are twice as expensive as software licenses that is why I mentioned a 50% increase is costs.
I understand the frustration, but want to correct this statement:
I consider service desk license and upgrade from software, and software an upgrade from core
This isn't accurate. Service Desk is not an upgrade from Software, and Software is not an upgrade from Core. They are three separate products, designed for different purposes, each of which can be used completely standalone. It's true that many companies use more than one, either separately or in combination, but that doesn't imply an upgrade relationship between the products.
Core is useful for companies without any development teams, who do not work in any kind of Agile format. It allows them to track work in Jira without conforming to the Agile conceit of Kanban or Scrum.
Software, on the other hand, was specifically designed to support Agile development and tracking. That's not to say that non-IT teams can't use Software; we do, because we also have IT teams so we already pay for Software.
Service Desk is configured for a specific type of work. Many companies only use Service Desk; they do not have any need for the other parts of Jira. Service Desk gives them an easy way to configure external customer access, set up custom request types without needing Jira admin experience, and, most importantly, work in queues the way a true front-line support team usually does.
Hi @Esther Strom. We have recently moved one of our software development projects into Service Desk JIRA (we have licences for both) in order to provide a much clearer visibility of all the workload of the team which includes software development, bug fixing and change requests - and provide easy communication back to individuals and teams requesting changes / bug fixes from within JIRA. However, I am struggling to see how we can deal with this work in an Agile way - I can't see how to set up a scrum board for example to manage sprints. Is this possible? I'm presuming some of the solutions suggested in prior years are not feasible any more.
@Simon Snell JSM (new branding; Jira Service Management) does not include boards or the functionality to manage sprints. That's not what it's designed for; it's intended for triage-style support that's managed via queues as issues come in, not on a scheduled (sprint) basis.
There are workarounds; you can create a Jira software project with permissions locked down so no one can create new issues in it, then create a board that runs off a filter that pulls in your service desk tickets. It's not ideal.
I'm not really sure I understand what "visibility" you gain by using service desk instead of Software if all of your users are internal.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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