Dave LIAO Community Champion

Does this happen in every single email notification coming from that support desk? Check the project settings, then "Customer notifications". Check each notification to see if the words "Testing" is present in any? 

@Stephanie Kohne - can you confirm if Victor is a member of any groups that might have admin privileges of any kind?

Ah, in that case, check if the user is a "Trusted User". These users have some admin privileges, and will receive certain admin email notifications, unfortunately. If this is the case, the user can relinquish their "Trusted User" powers and become a "Basic" user if desired.

It's possible the user who got notified was a project admin or project lead, but I'd need to verify that that case generates notification emails first...

What kind of email are they receiving? Can you add it here please? EDIT: If the user is getting a Jira-generated email that says "x project has been archived" (similar to this project has been moved to trash), these emails go to all users who are either "Trusted Users", or members of groups that have admin privileges.

Ah, this looks like a permissions issue. Since the path I see is a Windows path, check the instructions here: https://confluence.atlassian.com/jirakb/jira-server-throws-unable-to-create-directory-for-deployment-error-on-startup-389781040.html

What are you seeing when you try to start JSD? Any errors in your logs? 

Hi Dina! From what I understand about HIPAA, HIPAA compliance is possible within a Jira system - just ensure you are protecting patient info wherever that patient info will be stored. * Agree on where patient info should be stored. * Agree where patient info should NOT be stored. * Understand who should have access to…

@michael_martin - I'm guessing your JSD Server and Jira Cloud instances are both pre-existing? Any plans to merge them? Consider some of the Marketplace add-ons that allow for syncing between systems. Exalate's Jira Issue Sync (for example) can sync Jira to other systems, including other Jira's:…

@Shpendi Rakipi - there are JQL queries specific to SLAs you can use: https://confluence.atlassian.com/servicedeskserver041/using-jql-queries-specific-to-slas-969531109.html In particular, breached() probably will meet your needs?

To add to Danno's comment, if you're using Google's G Suite, Atlassian has a G Suite Marketplace app to give you context if any Jira Cloud or Bitbucket Cloud links exist in your emails: https://marketplace.atlassian.com/apps/1219311/atlassian-cloud-for-gmail?hosting=cloud&tab=overview

@Mahesh Chiliveri - hi Mahesh, are you using Jira Server or Jira Data Center? What add-on was used to enable SSO previously? If you're on Jira DC, this might help: https://confluence.atlassian.com/jirakb/bypass-saml-authentication-for-jira-data-center-869009810.html

When pasting email correspondence in Jira, ensure that the Visual editor is on. You won't be able to retain 100% formatting, FYI, but hopefully that works for you!

Can you elaborate on what you're trying to do? Is there SSO enabled on your Jira instance, and you want to temporary workaround it?

I wish there was a way to star articles and have them appear in your profile... I guess we can always just link to this from our profiles, eh? 😂

You're never too new (or too old) to contribute to the community! 🙏

@krhodes12 - if you haven't yet, sign up to learn about upcoming Philadelphia Atlassian Community Events!

* Does a Customer account exist for ticketsystem@companyx.com in your service desk? If not, try creating one and test again. * If you're an admin, go to the admin screen "Email requests", then check the log for your service desk - see anything that might help there?

Zoom out in your browser? Consider setting up Quick Filters to view slices of your backlog at a time (by label, component, etc.). Consider setting up Epics and filtering your backlog by Epic. Be sure to collapse the side panels (for epics, versions, etc.) when not using them to also regain some of that real estate. Hope…

In principle, having an orphaned Task map directly to an Initiative means there's an intermediate Epic that hasn't been defined: * The quick way out? Create a catch-all Epic. * The better solution (where possible) is to spend a little time to see what kind of Epic can be created to catch these Tasks. Either way will help…

Bummer, hopefully that changes one of these days? I submitted a JAC suggestion for that awhile ago 😉 https://jira.atlassian.com/browse/ID-240

@Akshay Aggarwal - field descriptions are only visible during issue creation in Jira Cloud. The default issue view in Jira Cloud doesn't support field descriptions (yet?) and editing all happens in-line. One workaround is to switch to the legacy issue view (the "old…

The Confluence permissions enhancements are much-appreciated. I just wept in delight 😁

@[deleted] - it's actually the "Create Issue" permission that controls whether a given user/group/role can see a project. In this case, the "Users" role is given Create Issues permission, which gives that role the *option* of creating issues within that project. Make sense? :)

Hopefully custom date fields will be supported soon? I know a few folks wondering about this. Appreciate any insight!

User impersonation saves so much time when troubleshooting issues - glad PS has this now!

As a workaround (at least with recent versions of Jira Service Desk), you can set the automation rule with "Issue matches", choose Advanced, then enter the JQL that the automation should trigger on. Hope this helps someone!

Super loco Jira behavior - I ran into this issue a year ago, and JUST ran into it again. Small surprises indeed. :p

If you do a remote session, happy to join!

I'm having the same issue - I can't actually get to an admin screen to force a directory re-sync though! Argh. :(