Is JSM a good choice for my case?

diego alonso_6o9pp9

Hello everyone!, I'm totally new to JSM.

I would like to know if you can guide me.

My proposal seeks to migrate the process to JSM and use Confluence as a repository, because I believe that the approach of request tickets, forms, automation and request management could work to improve the process.

---

This is the summary of the process and my proposal:

• I am looking for how to improve an application inventory update process which consists of requests and notifications, both via email. If the requester want to update, delete or submit a new application to the inventory, he have to fill an excel form and then request the app owner approval attaching the evidence .
• Then, send an email to the application inventory admin, with all the requirements  previously mentioned.
• If both, the form and approval are OK, the admin will update the inventory and then notify the requester.
• In addition, the inventory is available to the entire company in an Excel sheet.

---

Do you think that JSM is the best choice for this approach?

I'd really appreciate your help!.

Sorry if there are grammatical errors, English is not my native language.

Jeff Tillett

I think you're on the path to a great solution!

JSM would absolutely be able to accommodate your existing process, which is great, because minimizing change is a great way to improve adoption.

You could start by taking your existing process, and having the emails route through JSM for intake, notifications, and approvals. You could also publish your excel sheet to a confluence page and manage permissions. Most of this would "feel" the same to your end users, and provide a more streamlined, auditable, and easy to find "front ends" to the various bits of your existing flow.

Over time, you could use JSM's forms function to replace the Excel form, and even JSM's asset management utility to replace the excel sheet, and native confluence macros to replace maintaining a static attachment.