Dave LIAO Community Champion

@sumaiya.k - do you get that everywhere in Jira, or when you go to that specific URL? From the browser URL that I can see, it looks like you're trying to access a specific app (add-on) that might be misbehaving.

@Lauren Horncastle - hi Lauren! Reports (including pulling issue filter results) in Jira typically depend on (#1) when you run/access them, and (#2) your Jira instance's time zone. Regarding the second point, confirm your Jira instance's time zone. If you're an application admin, head over to Settings (gear menu) > System,…

@jira integración that's an interesting set up - you're using Jira Service Desk with ProForma Forms?

@[deleted] - go to your project's settings, then to "Customer permissions". Check the setting for "Who can customers share requests with?" - be sure to update it to "Any customer or organization, by searching in this project". Hope this helps! (If this helps, be sure to mark my answer as a solution!)

@Dnyaneshwar Ramesh Borase - in the link DavidF shared, the instructions on how to do that are there. Be sure to adjust the initialiser "defaultValue" contents to what you want as the default. :)

@CS - hi Connor! Try encasing your HTML content in a div tag, and use the same class JSD notifications use? Example: <div class="jsd-message-content"> your <b>cool</b> HTML here </div>

Faster reindexing? I can get behind that! 👐 For Jira Service Desk, could your team eventually allow "Request Participants" field to be added to permission schemes or issue security levels? Please? ♥ JSDSERVER-3948

@Timo Ketola - this might be a stretch, but have you tried adjusting Jira's "Internet Explorer MIME Sniffing Security Hole Workaround Policy" setting as detailed here? Internet Explorer isn't supported by Atlassian anymore anyway. :)

@Dave Curtis - go to the affected project's settings. Click "Request types". As a sanity check: * Confirm that the Request Type in the affected project has "EMAIL" under its name. * For that Request Type, click "Edit fields". Click "Request form". Confirm that Description is in the "Visible fields" section. * Click…

@Danielle Mayrberger - odd! Is this still happening? * If so, can you reproduce this issue across all 10 projects? * Try making a new Service Desk project. Does the issue occur in that project too? * To be clear, are the "customer notifications" settings reverting to system defaults? e.g. for approvals, "This request…

@IoT Solutions - can you screenshot or share an example notification you're trying to disable? Aside from Jira's notifications, there are Jira Service Desk-specific ones. (And then there are next-gen-specific ones too...) These articles might help. It would be useful to see which notifications you're trying to disable... *…

@Madhu mullangi - hi Madhu! * Are you using Jira Cloud, or Jira Server or Data Center? * Can you share the API call you're making?

If your situation allows, consider avoiding a project key rename. If you change an existing project's key, the old key won't be re-usable again when creating new Jira projects. The only way to free up the key would be to delete the project. Knowing that, if you have the option of creating a new project with the desired…

@Capital Careers - great, glad you were able to resolve your own issue!

@John Winstanley - If you run into the issue again, try checking https://status.atlassian.com/ - maybe there was an isolated server incident affecting some service desks?

@Capital Careers - * Which column are you checking for email id? * What's the code that you're seeing? Does it start with QM?

@Richard Morgan - when making an automation rule, under "Then do this...", click "+" then choose "Transition issue" to whatever your desired "closed" status is.

@Paul Stone - instead of inactivating a user, remove their application access so their user doesn't consume a license and incur a cost. (Via User Management, click into an inactivated user. Activate the user, but un-check any application access they might have had previously.) Try that with an inactivated user, then have…

@Sowmiya srinivasan - check out this answer: https://community.atlassian.com/t5/Jira-questions/How-to-get-all-sprints-in-project-using-JIRA-REST-API/qaq-p/525506

@Jh - you're lucky I ended my work day "early"! Finding out that Power Scripts (it's an add-on I'm a fan of) was part of your issue was also a pleasant surprise.

@Jh - yep, only users creating issues internally within Jira will notice this, and not via your service desk portal. ;-p Glad that adding the missing custom fields to the screen resolved your issue! Feel free to accept my answer (I'd love the recognition!), and TGIF. 🎉

@Jh - can you re-confirm? In issue SICHD-436 that you referenced, does the missing custom field now exist in the Create screen for that issue type?

@Jh - actually, before making modifications, you mentioned "the custom field is not in scope of this project or screen". Can you add any missing custom fields to the screens used for that project?

@Jh - you can update the script to run only when the custom fields are present. Use this routine: https://confluence.cprime.io/display/SIL/isCustomFieldInContext This Community thread also references the same problem you're having…

@Jh - like I mentioned earlier (in my now-edited previous answer), ensure the referenced custom fields all exist so Power Scripts doesn't get confused. * check the request form - what issue type is mapped to it? * check the issue type screens, do the custom fields exist on them?

@Jh - ah, Power Scripts! Do those custom fields exist in the affected project? Do they exist on the request form(s) and the screens for the issue type(s) used in those request form(s)?

@Jh - have access to your server logs? If not, find someone who does, and share the exact error(s) you see there.

@Jh - any changes in your network setup or architecture, like an SSL certificate. But never mind that question since you confirmed that other Jira projects are operating without issue. Can you temporarily create a new request type in the affected project, with just one field (like Summary), and see if that works?

@Sowmiya srinivasan - yes. A few notes: * To find issues for multiple users, use Assignee IN (username1, username2). * You might need to replace sprintId with just Sprint. * Sprint IDs are global, so you can exclude "project" from the JQL query. Try something like http://localhost:8080/rest/api/2/search/?jql=assignee IN…

@Jh - * This is a Jira Server instance, not Jira Cloud, right? (Your Jira URL doesn't end with atlassian.net, yeah?) * Has anything changed in your network lately? This creation fails from an incognito window too?