Tuncay Senturk _Snapbytes_ Community Champion

Great, I see that using the start date in the JQL returns results as expected. So, do you mean that JQL runs OK in the issue navigator but it doesn't work via the Python script? 

Is this "Start date" that we see on the screenshot the cf[10015]? If yes, these rows indicate that they are July 01, so we don't expect them to be between 2025-08-01 and 2025-08-31. My second question, are you sure that it's a Date field?

Hi @Marc Welcome to the Community! I am unsure if I understood your problem. Are you sure the customfield's value is not null, check adding this to the JQL AND cf[10015] is not EMPTY If this customfield is date only custom field can you make sure that you are using YYYY-MM-DD format?

You're welcome!

Hi @Francesc Juventeny In Team-Managed projects, the translation screen shows statuses that are actually mapped to request types in the portal. Go to Project settings -> Request types and make sure each status you want to translate is part of a workflow connected to a request type. You may need to temporarily map them to a…

Hi @karin_hardison Welcome to the Community! You can see changes either through the UI or via the REST API: - If you go to the specific Object Type witihin the Schema of your asset, click the History tab. You can then filter by object key. It returns the change history similar to the Jira work item changes (old value ->…

Hi @Stephen Call You can get using diff() between two date/time fields (see how you can use diff function here in detail), then format the result for days/hours/minutes with toDuration or string formatting before passing it to the “Log work” action. For business hours, Jira Automation doesn’t natively support excluding…

As far as I know, it doesn't support pretty-printing JSON natively. When you use {{webhookData}}, it's always inserted as a single-line minified JSON string. I hate doing this, but I usually pre-format the JSON as a string with line breaks (\n) and indentation before it’s sent to Jira, which is a burden.

I am glad it helped!

Hi @Sudesh I could not find any public documentation defining @Beta, but across Atlassian libraries, it consistently means: “This API is experimental and may change in future versions without notice. Use at your own risk.” Jira Rest Java Client source code annotates it, and IMHO, using the REST API directly is safer and…

There should be Assets Object customfield. See this Article. If this is Data Center, it might be seen as Insight Object/s. You can configure the IQL filter to restrict selectable assets.

Hi @Wenjing Liu Insight already provides an object picker field. Why don't you use it and try to implement a new customfield?

I am glad it worked!

Hi @Wenjing Liu The root cause of the problem is the line below: options.add(ComponentAccessor.getOptionsManager().createOption(fieldConfig, null, Long.valueOf(id), key)); This line creates new Option instances every time the field is rendered. Every time this code runs, it adds the new Option to the database.You must…

Hi @Sara Beaudet Welcome to the Community! These are really interesting insights, thanks for sharing! I’ve been exploring the remote SSE server too and found your points about tools vs resources and how different clients handle them especially helpful. Curious to see how Atlassian evolves this, it feels like there's a lot…

Hi @Sharad Regoti Welcome to the Community! The /relatedwork endpoint isn't designed to return the list of issues within a version, it's the related issues for the given version id. You can add links to a version using the new Related work feature! You can use the below JQL search endpoint to get those work items within…

Perfect! That's an even better solution.

Hi @Vladimir Bershtein Welcome to the Community! As far as I know, JSM links the request to the organization internally, which allows users in the same organization to see the ticket in the portal if “share with organization” is enabled. However, this does not populate the “Organizations” custom field. So, I'd recommend…

Hi @durso Welcome to the Community! This is a known limitation in JSM. SLAs do not reset when using the Recalculate SLA action unless the issue goes through the defined SLA start condition again. It only rebuilds the SLA, it does not reset/restart by comments or any actions (which don't match the SLA start condition). You…

Hi @Vanessa Friedrich Welcome to the Community! As already mentioned, Jira Cloud does not natively support this. I'd also like to recommend a free app SnapMetrics – Real Time Analytics, (I am one of the people behind this app), it’s a free app that can do exactly what you're looking for. - You can define a Time Between KPI…

Hi @Christopher Diaz As @Pramodh M and @pawarsachin84 said, there is no built-in solution for it yet, and you need to use an app for that. If you are interested in using a free app, I'd suggest SnapMetrics - Real Time Analytics on the Marketplace. I am one of the people behind this app, so let me know if you need further…

Hello @Adam Setch Thanks for sharing this — looks really helpful! Very kind of you to make it free and open source, I’m sure many in the community will benefit.

Hi @nathalie_talis You can achieve it by using Automation Rules as @Trudy P Claspill mentioned. However, I suggest checking out the free app SnapAssign. It's specifically designed to assist with smart assignments based on teams, schedules, and other rules. It allows you to simply define rules for your teams, and whenever…

Hi @KUMAR TRNVNP BEZAWADA I believe you'll receive more answers if you post this question on the Atlassian Developer Community.

Hi @marcin.lenarczyk Are you encountering an error? If so, what specific errors are you facing? I have been using the jql-editor's 2.0.1 version (not the thin wrapper but the original one) with React 18.3.1 without any problems.

Hi @Charlie Gunyon Sorry for the late response. I'm not sure if you already found the resolution but here are my two cents on this. It seems that, this is likely due to payload truncation. Jira has internal response size limits (possibly ~200k), and expand=changelog can be the root cause for inflating payload size quickly.…

Hi @Daniel NA As far as I know, triggering a UI refresh in the backlog view is not officially supported via public JavaScript APIs. JIRA.trigger is mostly for classic views and not effective in agile boards.

Hi @Tetiana Bondar Building on what @Trudy Claspill says, I've checked the Atlassian changelogs and couldn't find any deprecation notice related to this. Could you please clarify why you think it has been deprecated?

Hi @AlterEgo Have you tried adding the projectKey to the mapping file? - endpoint: POST /rest/raven/1.0/import/execution/junit/multipart - Add projectKey to the mapping.json { "testExecutionKey": "PROJ-5595", "projectKey": "PROJ", "tests": [ { "testKey": "PROJ-5414", "testInfo": { "name": "testA" } }, ... ] }

Hi @Assem E These sorts of Javascript errors are very tricky to find their root cause. It could be a browser cache issue or a broken customisation, such as a ScriptRunner script or a faulty plugin code (a recent update of a plugin). Are all users experiencing the same error, or is it only one user? Have you tried clearing…