Activity
Mon
Wed
Fri
Sun
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
What is this?
Less
More

Memberships

Atlassian Everything

245 members • Free

1 contribution to Atlassian Everything
JSM emailed requests - best practices
We’re planning to set up a Jira Service Management (JSM) project to handle internal (business) requests in a standardized way. Today, these requests come through a shared mailbox ( Shared mailbox is Microsoft 365 outlook.), but as the team has grown it’s no longer sufficient for tracking ownership, prioritization, reporting, or SLAs. Question: What’s the recommended/best-practice approach for setting up JSM for internal requests? Set up email forward rule ? or add external email address ? What are the prerequisites, if we need to add shared mailbox as " add external email" ?? Common pitfalls when moving from email to JSM If you’ve done something similar, please help share your ideas. Thanks in advance!!!
1 like • 20h
1. Agree that moving away from email submissions is the best path 2. Document the new process and add a link to it in the form! 3. If you have some sort of Go or URL shortener, use that to give people a quick memorable way to jump to the portal/form. 4. Communicate users can find their requests after they submit (this one can be a struggle for teams that aren't use to using Jira so I recommend comms/documents/videos. 5. Outline the expect SLAs so there is an expectation of updates and users don't feel like they end up in a void.
1-1 of 1
Sara Tucker
1
2points to level up
@sara-tucker-2406
Atlassian org admin - Knowledge management nerd

Active 4h ago
Joined Nov 11, 2025
Powered by