currently, we handle all our internal IT requests via Jira. We are thinking about moving everything in regard to our Internal IT to Jira Service Management. My questions, therefore, are:
I would welcome it if anyone that has already done something similar can give me some advice. Thank you very much.
I would create a new JSM project and try to share settings with the existing project you have. This will result in having certain shared schemes, such as notification, screen, permission, issue type, workflow etc. This will be very handy, since you don't want to lose any data (data are stored in fields, and fields live within screens).
The check I would perform before moving any issue to the new JSM project would be:
I think that's about it. BUT before doing any of the above, may I ask the reason behind moving to a JSM project? Are you going to add all your employees as customers? If yes, then you have to set up your JSM project as well.
Hope all the above helps.
@Alex Koxaras Thank you very much for your fast reply and the information you gave me on what I should look out for.
BUT before doing any of the above, may I ask the reason behind moving to a JSM project? Are you going to add all your employees as customers? If yes, then you have to set up your JSM project as well.
I believe that you are in the right direction, considering all the inputs you provided here. The reason I asked you, is simply because there was no apparent reason for you to move, and save all the trouble. However, as I said, you are correct in considering moving to a JSM project.
You can use the free plan to cover your needs, but make sure that the free plan has all that you need. Setting up a JSM project has to do with:
that is exactly the point why I am asking because it could potentially take a lot of time to get everything just right with JSM. If it is worth it, we will see. I just wanted to make sure that all the variables are considered. Personally, I would prefer setting it up because, in the long run, it seems to be a better way of handling issues like that.
Anyway, thank you very much, I think I got all the information I needed.
There is one small catch in what Alex has said. When you are checking the permission scheme, you need to be aware that JSM projects handle users differently and the permissions for a Software or Work Management projects are usually not suitable for JSM projects. You can end up with Jira complaining that there are errors in your permission scheme that make your JSM project non-functional. It can correct them for you, but that means overwriting what you've set up.
So when you're checking the permissions are the same, what I would do is create a JSM project and apply its permission scheme to your existing development project - that way, you know you'll be migrating stuff that won't break your new project.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
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