I wanted to get some guidance and direction on how to structure teams/departments in Jira/JSD. Currently, our developers are using Jira Software and have encouraged our service desk to deploy JSD. The Service Desk is now evaluating JSD but was curious as to how to structure teams. By structure, if we take the Network Engineering department, would they be setup under JSD or JSW? Same goes for the DBAs for example.
It is important that we structure this currectly so that we don't have to change things in the future. What has your company done for this?
before I can give you my $0.02 worth I need more info. Too I'm not sure what you mean by "...would they be setup under JSD or Jira Service Desk?". Did you mean to ask if they should use JSW or JSD or something else?
Again, with a bit more understanding of your organization and needs I could provide more useful info.
Thank you for your reply and pointing out my mistake in my post. I have fixed it in my original question.
1. JSD customers and users will all be internal (would deploy for external use at a later point but still only used for inernal employess).
2. Yes we plan to use both side by side.
3. What I mean is that, in our current tool for example, under incident management we can assign an engineer/team a task to complete in order for our incident to be able to close. If we take network engineering as an example, they would log into our current tool to work on the task and resolve it once it is complete; notifying the incident owner. In our current tool, everyone is set up under the one tool, but seeing JSW and JSD, the question they have is should all the teams other than service desk be in JSW or if IT departments/teams (Networking, Telecom, DBA, Server, etc.) should be in JSD while development (Web, Internal Tools, QA, etc.) be in JSW.
Thanks. So FWIW, here is how we use and others seem to use in a similar fashion.
I use JSD to service the entire organization as "customers". Customer open job requests and/or report issues. I use JSW for business and SW processes. If an issue opened in JSD translates to one of my business or SW processes then the agent creates a linked issue from the original to the appropriate project. Here are some examples that might help...
We use linked issues rather than Moving them out of JSD to JSW so that the Customer (originator) doesn't loose site of the issue. There are ways, thru automation, to resolved the JSD issue when the JSW issue is resolved.
The key reasons I choose to use JSD rather than JSW for a projects include:
I use JIRA for the following reasons:
there are a lot of things to consider and I will say that I find myself thinking thru which way to go on some new projects that pop up but in the end the above generally guides me.
more or less that is the case. my IT group acts as 'customer service' group for internal issues be that pure IT or business applications (3rd party or homegrown tools). That said the JSD agents are also members of JSW for various reasons. Conversely, the JSW users are not JSD agents but some are Collaborators on JSD issues (can comment and view but not otherwise edit/transition).
Yes I would say your network engineers would work w/in JSD. I think you will want to give them JSW access to, at least if they will need to create issues in JSW, e.g. the create linked issue scenario.
...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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs