Tuncay Senturk _Snapbytes_ Community Champion

If nothing happens when customers email your JSM project, then you may - check project settings → Email requests, and make sure the address is connected and active. - ensure the people sending the email are either customers of the project or your project is configured to receive requests from anyone. - ensure each incoming…

I don't think you're doing anything wrong. I believe this is an intermittent problem with Jira’s new cursor-based search, as there are others who are facing similar issues. https://community.atlassian.com/forums/Jira-questions/REST-The-new-rest-api-3-search-jql-endpoint-is-a-complete/qaq-p/3101716

Did you try using regexp? {{raw.match("\"StarterName\":\"(.*?)\"")}} It should return Jill Hampson. Or, if you want to use substringbetween make sure your delimiters exist exactly in the raw text. I think the below would work {{raw.substringBetween('"StarterName":"','","StartDate"')}}

Hi @Trevor Long I think you need to extract just the hour in 24h format after conversion and compare it {{now.convertToTimeZone("America/Chicago").format("HH")}} That will return values like 06, 14, 23, etc. You can then add conditional checks such as: If >= 06 and < 17 → assign to 1st shift If >= 17 and < 02 (next day) →…

it sounds like the problem is isolated to the Xray app and not Jira itself. I'd suggest raising a ticket to Xray support

Hi @Shoham Egozi I think you’re getting an internal error rather than something specific to your project. Because the error message includes a Hash and Trace ID and generally these means the error is on Atlassian side. However, - Have you tested using a different browser or in incognito mode? - If it only happens with a…

Hi @Iuliana Goncharenko Could you share a bit more detail about what happens when you try to create the request by email or via the API? For example, are you seeing any error messages? With a bit more info, we can help pinpoint and fix the problem.

My bad, sorry! Jira 10.x requires Java 17 but not jakarta imports (not yet for 10.3), On Platform 7, Atlassian moved many deps to Jakarta but kept javax.* package names. Switching to jakarta.* will come later on Platform 9. So, use provided javax.servlet as the below <dependency> <groupId>javax.servlet</groupId>…

Hi @Ravi Saurav Your REST resources can still use Spring Scanner + @ComponentImport after upgrading to Jira 10.3, but you must migrate to Jakarta packages and have Spring Scanner correctly configured. See release notes here. - javax.servlet.* → jakarta.servlet.* (your servlet must extend jakarta.servlet.http.HttpServlet).…

Hi @Mina Amer , The base price you’re quoting ($42,000/year for 500 users) is the public list price for Jira Data Center, and that applies whether your deployment is connected to the internet or fully air-gapped. There isn’t a special “offline” surcharge from Atlassian. No additional offline surcharges from Atlassian, but…

Hi @Troy Anderson {{^last}} is evaluated against the original loop, not your filtered output.Because you’re skipping items inside the loop with #if(...), the item you print last usually isn’t the actual last element of the collection. so {{^last}} is still true and you get a trailing comma. Fix it by making the loop only…

You're definitely not alone in facing this challenge and JSM doesn't natively support assigning issues directly to a group or team. Using sub-tasks or queues can help distribute work visually, but they don’t solve the core problem of automated smart assignment especially when considering availability, rotations, or…

For the Worklog Report, you can filter by groups or users. However, if you need to group by team (a custom field), that is not available at the moment; grouping only works with epic, user, issue, component, and fix version. But we will raise an internal ticket and release a new version that includes the custom field…

Hi @Juan Falguera Sorry to hear that, but that seems to have been a cache issue as we have already launched the latest version fixing the problem. Could you please refresh the page (preferably with Ctrl + R) so the latest version runs? Thanks

Hi @Leandro Naranjo Unfortunately, you are correct. Atlassian has recently removed the API, which is why the reports suddenly stopped working. Since the app’s Marketplace listing is no longer available, it looks like the app may not be supported (as I could not see any announcement). If you are looking for an alternative,…

Hi @Florian Kreutzer I can't say I got it 100%. Which product are you using for Goals? What exactly is the goals metric you want to automate?

Hi @maxine_hu I see that this is Jira DC. This happens when static resources aren’t loaded properly or are corrupted in cache. And usually cleaning the browser's cache resolves the issue. However, you mentioned that it did not work with other browsers either. I'd suggest trying with Chrome's Incognito mode and if it still…

Sorry, I wish I could assist at this stage but I can't as I don't know the answer

That's a good question that I do not know the answer exactly :) However I can share a code that might be helpful for you, but please be aware that I haven't tried this code, it's just the code I am adapting some code of mine and writing it here CustomField cf = customFieldManager.getCustomFieldObject("customfield_xxxx);…

The error is coming from those io.riada imports. Those packages aren’t exported by the Assets bundle. I'd suggest removing all io.riada packages and using com.riadalabs.jira.plugins.insight.channel.external.api.facade.*and the public model com.riadalabs.jira.plugins.insight.services.model.ObjectBean.As far as I know from…

Hi @Wenjing Liu That error means your plugin is importing packages that Jira don’t export. Adding those packages to <Export-Package> in your bundle won’t fix it. Long story short, you can’t export classes you don’t own. Only export your own API (if another plugin must import it).

Hi @Wenjing Liu Are you sure this is for Jira Cloud? That stack trace is from Jira Data Center, not Cloud. Jira Cloud apps can’t load OSGi bundles at all. You must use Forge or Connect for Cloud custom fields.

Your logs tell something. Sorry if I'm misleading you though With proxy, 503 service unavailable - the proxy is rejecting CONNECT to your Jira. Mostly, it needs enterprise authentication (Kerberos/NTLM) or the Jira host isn’t allowed. Without proxy. 10054 Connection reset - something (WAF or load balancer) is closing the…

Thanks—that narrows it down a lot. If curl works but requests not, it can be CA trust issue or proxy problem. You may need to import ca-bundle cert file for a hardened requests session.

Hi @rAJ It seems to be a network / TLS / proxy issue rather than an HTTP 401 or 403. From the same host, you can simply run a curl command to https://jira.vtxxxxx.net/rest/api/2/serverInfo , if this also resets, it’s network/TLS/proxy, not your code.

Hi @Antonia SLAs are driven by the start/stop conditions, not by the issue’s Due date field. Changing the due date won’t automatically shift the SLA target. If you want the SLA target to move with the due date, you can change the SLA’s stop condition so it’s calculated relative to the Due date. Or you can use automation to…

I see! That really depends on how you’d like to handle it. You could filter issues by Start date and exclude any work logs that fall outside the range (you’d need to add an if statement in your script for this), or you could filter issues by worklogDate directly in your JQL. Keep in mind that an issue can have multiple…

I suppose you intentionally removed the assignee's right part. If not, that's a problem. Considering the fact that this JQL is generated by the code, this MUST work. Removing created and updated fields and leaving only the cf[10015] equation should work. Since that's the date field and the date part is generated correctly…

I don't think sharing the final JQL from the code breaches confidentiality. I just need to see the JQL that is run via the code (to verify that the date values are assigned in the correct ISO format and also to check quotes and parentheses).

Yes, of course it's OK to use any field/custom field in your query. Could you log the JQL which is generated by the script? Seeing the final generated JQL (before executing) will help us have a better idea.