JKM Tech Notes

IT notes, tools, and practical how-tos for Atlassian and everyday tech.

📧 Important Email Update for Namecheap Users: ActiveSync Discontinuation

22/07/2026

If you’re using Namecheap Private Email with ActiveSync on your phone or tablet, here’s a critical update you need to know about. 🚨

🔔 What’s Happening?

Namecheap is discontinuing ActiveSync support on August 3, 2026, as part of their migration to a new Private Email webmail platform.

This change affects users who currently sync their email, calendar, and contacts using the ActiveSync (Exchange) protocol on mobile devices.

⚠️ What This Means for You

If you’re using ActiveSync:

Your mail, calendar, and contacts will stop updating automatically on your mobile device after August 3, 2026
You’ll need to reconfigure your email app to continue receiving messages

Note: Your Private Email account and all your messages are safe — this only changes how your device connects to the service.

✅ What You Need to Do

To keep your email working, you’ll need to switch to IMAP/SMTP for email and CalDAV/CardDAV for calendar and contacts. Here are the exact settings:

📥 Email Settings (IMAP/SMTP)

Setting	Value
Incoming server (IMAP)	`mail.privateemail.com`
Incoming port	`993`
Incoming encryption	`SSL`
Outgoing server (SMTP)	`mail.privateemail.com`
Outgoing port	`465` or `587`
Outgoing encryption	`SSL`
Username	Your full email address
Password	Your email password

📅 Calendar & Contacts (CalDAV/CardDAV)

Service	Server
Calendar (CalDAV)	`dav.privateemail.com`
Contacts (CardDAV)	`dav.privateemail.com`

🛠️ How to Reconfigure Your Device

On iOS (iPhone/iPad):

Go to Settings > Mail > Accounts
Remove your existing Namecheap account
Tap Add Account > Other > Add Mail Account
Enter your details and use the IMAP/SMTP settings above
For calendar/contacts, add separate CalDAV/CardDAV accounts using the servers listed

On Android:

Open your email app (Gmail, Outlook, etc.)
Remove the existing account
Add a new account using IMAP settings above
Most Android email apps support IMAP natively

On macOS Mail:

Namecheap has specific guidance for Mac users, you can access it via webmail by clicking the Gear icon > Connect Your Device > macOS for step-by-step instructions.

💡 Pro Tips

Test before August 3: Don’t wait until the deadline – reconfigure now to avoid disruption
Backup important emails: Use your webmail at privateemail.com to verify all messages are accessible
Calendar migration: If you have existing calendar events, you can export them as .ics files from your old setup and import them into the new CalDAV configuration

🔗 Helpful Resources

📝 Why I’m Sharing This

I use Namecheap for my domain registration and received this notification hence I wanted to share this with my blog readers in case anyone else is affected especially since this change is coming up soon! 🙌

🔧Navigating JSM Space Settings: Request Management > Request Types, Forms & Workflows 🔖

03/07/2026
In the previous post, we have discussed the Access settings. Now, we will dig about Request Management which will show the first part for Request Types, Forms & Workflows.

Under Space settings > Request management, find Request types, Forms, Workflows. This is where ITSM shines, you can customize what customers see in the portal vs. what agents handle.
- Request types: Pre-loaded gems like “Get IT help” or “Incident.” Preview, add/remove during setup.
Updating Request Types 📝

Request templates (aka types) control forms. Here’s my go-to process – saved hours on custom hardware requests:
1. Go to Space settings > Request management > Request types.
2. Pick a type (e.g., “Service request”).
3. Edit name/description directly – what customers see in portal. Hit Save changes.
4. Switch to Request form (customer view) or Work item view (agent view).
5. Drag & drop fields:
- Add from right panel (e.g., “Asset tag” custom field).
- Remove/reorder as needed.
- For forms: Tweak Display name, add description, set preset value & hide, or mark Required.
Save changes – test in portal immediately!

Adding Request Template 📝
- Go to Space settings > Request management > Request types.
- Pick a type (e.g., “Service request”).
- Click Create request type.
- You can choose from templates or you can create your own. I created my own for my Offboard Employee request type.
Drag & drop fields:
- Add from right panel (e.g., “Asset tag” custom field).
- Remove/reorder as needed.
- For forms: Tweak Display name, add description, set preset value & hide, or mark Required.
- Once saved, you should see this little window and click View in Portal to test.
- Try to add information from that portal to test and click Send.
- This is how it looks like from the requester’s side:
- And this is how it looks like on the Agent’s / IT Service Desk Space’s side. You can configure other settings as you wish.
Adding Forms and Workflows to Request Types in Jira Service Management 🛠️

After setting up my Request Types in Jira Service Management, the next step was making them more useful by adding Forms and connecting the right Workflows. Request Types are already in place, so this part is all about improving the customer experience and making sure every request follows the right path behind the scenes.

Adding a form to a request type 📝

Forms can be attached directly to a request type so customers only see one clean request form when they raise a ticket. Atlassian documents two main ways to do this: attach a form from the Request types area, or attach it from the Forms builder settings.

My usual setup flow 🔧
1. Go to Space settings.
2. Open Request management.
3. Select Forms.
4. Click create form.
5. You can add a new from a template or create a blank.
6. Then you can attach the form in a certain request type.
7. Save the changes and test the portal view.
- I had added an International Roaming Request (from a current template) for my Request for new sim card or roaming request type.
- So this is how it looks like from my request types:
- And here how it looks like from the IT Service Desk live portal:
Connecting the workflow 🔄
- 🔹 Every request type in Jira Service Management is tied to a work type, and each work type is tied to a workflow.
- 🔹 On the surface, a request type may look simple, but underneath it’s routed through a workflow that controls statuses like To do, In progress, and Done.
- 🔄 This is where the request starts feeling like a proper service process instead of just a form submission.
- 👥 The workflow decides what happens next, who can act on the ticket, and how the work progresses internally.
- ✅ If your request types are already created, this is the stage where you double‑check that each one is connected to the workflow that fits its purpose. ⚙️
Quick Tips 🚀
- Permissions: Space admin only. Share wisely via People.
- Test Always: Portal preview avoids “oops” tickets.
- Scale Smart: Company-managed for shared schemes; team-managed for simplicity.
- Resources: Customize request types | Edit space details.
🖱️ Logitech Signature M650: When My Dongle Wouldn’t Reconnect After Bluetooth Pairing

23/06/2026
I recently ran into a frustrating issue with my Logitech Signature M650 wireless mouse after pairing it to my work laptop over Bluetooth (BT), my dongle connection through the docking station stopped behaving the way I expected.

I mean I know the receiver would not work because it has been paired via BT when I came back to my desk, but reconnecting it was not as straightforward as I thought. Logitech’s Signature M650 supports both Bluetooth Low Energy and the Logi Bolt receiver, and Logitech’s support pages also note that the mouse can be paired through either path depending on your setup.

What happened

My usual setup is simple: the USB receiver stays plugged into the docking station, and the mouse works normally at my desk. If I switched from personal Mac laptop to work laptop (Mac too) it will just work straight.

But when I moved away from the dock, I paired the mouse directly to my work laptop using Bluetooth. When I returned, I removed the BT connection from my work laptop and re-paired the dongle connection to take over again, but it did not reconnect cleanly.

I tried using Logi Options+ first because that is the app many search results recommend, but it did not solve the problem.

If you pair it via BT from one laptop, then pair it with another laptop, and if they are on the same range it will not work that is why I need to use the dongle receiver via docking station.

What I tried

After a bit more searching, I found a few ways to get the mouse and receiver talking again. These are the main options I came across, and they are useful depending on the type of Logitech receiver you have and the operating system you are using.

Option 1: Web-based pairing
If you have a modern Logitech receiver such as Unifying or Bolt, you can use Logitech’s browser-based pairing flow instead of installing a full app. The basic idea is to plug in the receiver, open the pairing tool in your browser, choose the receiver, then put the mouse into pairing mode by turning it off and back on.

Use Chome and paste -> https://logiwebconnect.com/ click Continue

Click Select a Receiver

Once Receiver is paired, add a device (so this will be your mouse) and follow the instructions (clicking the left/right button)

Paired successfully!

Option 2: Standalone connection utility
Logitech also provides a lightweight connection utility for some older devices. This route is simpler than installing a larger software suite, and Logitech’s support documents still reference legacy connection tools even though they are no longer actively maintained.

Works with Windows only https://support.logi.com/hc/en-us/articles/360025141574-Logitech-Connection-Utility

Option 3: Bluetooth only
Since the Signature M650 supports Bluetooth Low Energy, you can skip the dongle entirely and pair it straight to your computer. Logitech’s setup guide says to turn the mouse on, hold the connect button until the light blinks, then pair it through your system Bluetooth settings.

The fix that worked

Option 1 worked best for me. The browser-based pairing approach was the one that finally got my Logitech receiver working again without forcing me to rely on Logi Options+. That was the big lesson here: sometimes the most effective fix is not the most obvious one.

Practical tips

If you run into the same problem, these are the things I would try first:
- Confirm whether your mouse is paired to Bluetooth or to the receiver.
- Make sure the receiver is connected directly and is recognized by the computer or dock.
- Try Logitech’s browser-based pairing flow before installing extra software.
- If you do not need the receiver, Bluetooth is a clean backup option for the Signature M650.
Final takeaway

My main takeaway is simple: the Logitech Signature M650 is flexible, but that flexibility can create confusion when you move between Bluetooth and receiver-based use. For me, the dongle reconnect issue was solved by using the web-based pairing option, not Logi Options+. If you use the same mouse on a dock at one moment and Bluetooth on a laptop the next, it is worth knowing all three recovery paths before the frustration starts.

Useful references: Logitech’s Signature M650 getting started guide, Logitech’s Bluetooth setup guide, and Logitech’s Unifying receiver setup page.
🔐 Navigating JSM Space Settings: Access ⚙️

20/06/2026
In our previous post, we explored the Details, Summary, and Features of a Jira Space. Covering how to set up your space identity and configure key capabilities. Today, we’re diving into the Access settings, your control centre for who can do what inside your space. 🎯

To get there: Space Settings → Access 🛠️

👥 People and Access

This is where you manage who is in your space. You can add people individually or by group, and assign them a role (like Viewer, Member, or Admin) that controls what they can do. Think of it as your space’s guest list — you decide who’s in and what they can touch 🙋.
- Select Add people → search by name, group, or email
- Assign a Role from the dropdown
- Remove access anytime from the same page
🛡️ Space Permissions

This is the deeper permissions layer — it maps specific actions to users, groups, or space roles. Rather than just assigning a broad role, Space Permissions lets you get granular. Examples include:
- 👑 Administer Spaces — full space control
- 👀 Browse Spaces — the gateway permission; users need this to see anything[3]
- 🔄 Edit Workflows — update statuses and transitions
- 📦 Manage Versions — handle releases
- 🏃 Manage Sprints — start, complete, and adjust sprints
⚠️ Browse Spaces is critical — without it, nothing else works.

🎧 Customer Permissions

Specific to Jira Service Management (JSM), this section controls how customers (i.e., end users raising requests) can access your service portal. You can define:
- Who can raise requests — anyone, invited users only, or specific accounts
- Whether customers can share requests with other customers
- Portal visibility and signup settings
This keeps your service desk secure while staying accessible to the right people 🔒.

🔒 Work Item Security

While Space Permissions controls space-level access, Work Item Security goes one level deeper — controlling who can see specific work items within the space. Using a Work Item Security Scheme, you can hide individual issues from users who don’t need to see them, even if they’re already in the space.
- Users not assigned to a security level won’t see those work items — even with Browse Spaces access
- Levels can be granted to space roles, groups, individual users, assignees, reporters, and more
- Requires the Set work item security permission to use
Perfect for sensitive tickets like HR requests, security incidents, or executive escalations 🕵️.

That covers all four sub-sections under Access in JSM Space Settings. Set these up correctly from day one and you’ll have a well-governed, secure space without the permission chaos later! 🔐✅
📋Navigating JSM Space Settings: Details, Summary, and Features ⚙️

03/06/2026
If you’ve ever opened up Jira Service Management and wondered where to tweak the essentials of a space, you’re not alone. In this post, I’ll walk through the first parts of JSM Space Settings: Details, Summary, and Features, and show how each one helps you keep a service space organised, useful, and ready for real-world IT work.

Navigating to Space Settings 🧭

Start simple: In your JSM space sidebar, click More actions (- – – ) next to the space name, then Space settings.

Boom – you’re in the hub!

Details: The basics first 🧩

This section is where you update the core identity of your JSM space. This is where you can change things like the space name, key, category, and icon, which is useful when you want the space to reflect your team, service, or business unit more accurately.
- Admins only for key changes like space key (must be uppercase letters/numbers, 2+ chars).
- Always backup first!
- You won’t be able to create a new space with a space key that has been used previously.
- Previous space keys are saved to ensure that any links, filters, and queries using your previous keys continue to work.
- Atlassian is currently exploring solutions to allow previous space keys to be reused.
Summary: A quick view of the work 📊
- The Summary page gives you a high-level overview of what is happening in the space.
- Atlassian describes it as a dashboard-style view that can show key metrics such as work items created, updated, completed, and due soon, along with charts that help you understand workload and progress.
Features: Turn capabilities on 🛠️
- The Features section is where you enable extra functionality for your space.
- Atlassian notes that this area also includes the Feature Lab, which is where you can test newer ideas before they become standard parts of Jira Service Management.
- This is the part of the settings page that gives admins the most flexibility.
- Depending on your setup, features can include things that improve request handling, access, channels, and other service-management capabilities, all of which help your team work more effectively.
If you are managing Jira Service Management spaces, getting comfortable with Details, Summary, and Features is a great place to start. These three areas cover the essentials: how the space is identified, how work is reviewed, and how functionality is enabled.

Once you understand them, navigating JSM space settings becomes far less intimidating. It is one of those small changes that makes a big difference in how smoothly a service desk runs day to day.

Will cover more of the Space Settings in our next posts so stay tuned!

I am learning, we are learning!💪🏻 We keep learning!🧠