Comments
-
Unfortunately, JQL does not preserve the order of the issue keys specified in the IN() clause. It only filters the results. You can sort them using ORDER BY with a Jira field, but displaying them in a custom order such as ISSUE-4, ISSUE-2, ISSUE-31 is not supported by standard JQL.
-
Hey! This is a common point of confusion when setting up Assets for the first time. You’ve already done the hard part (creating your object schemas and populating data). Now you just need to create and configure an Assets field so you can link assets to your work items: Go to Jira settings → Work items → Fields. Click…
-
Hey! This is a common point of confusion when setting up Assets for the first time. You’ve already done the hard part (creating your object schemas and populating data). Now you just need to create and configure an Assets field so you can link assets to your work items: Go to Jira settings → Work items → Fields. Click…
-
@Thorsten Letschert _Decadis AG_ Absolutely agree with this! Jira’s flexibility is both its biggest strength and its biggest challenge. I’ve learned the hard way that adding “just one more” custom field or workflow tweak can snowball into a complex, hard-to-maintain setup. And most importantly, Jira won’t fix broken…
-
As someone managing complex integrations between Jira Assets and external systems like Azure AD, Intune, SCCM, and Meraki, my advice to new Jira admins is: - Document everything from the start: whether it's custom field usage, automation rules, import mappings, or API tokens. Clear documentation in Confluence has saved me…
-
Thanks for clarifying, @Ondřej Medek . I completely agree with your point about the roadmap. From my side, while I understand and support the intent behind the terminology change, the lack of a clear migration path is what worries me the most. As you mentioned, permissions and other core parts of Jira still reference…
-
Thanks for sharing this update. I understand the goal of making Jira terminology more inclusive for different teams, and I see how using “work item” can make sense beyond software development. However, I share some of the concerns mentioned here, especially around automation scripts and integrations that heavily rely on…
-
This one worked fine for me { "attributes": [ { "objectTypeAttributeId": 2938, "objectAttributeValues": [ { "value": "2024-09-18T00:00:00.000Z" } ] } ]}
-
Hi, @Timothy Brown. Not sure if this help, But I have this scheduled task that run my job, cleanse and import to Data manager so I have my dashboard updated everyday: # Función para ejecutar comandos y verificar logs function Ejecutar-Comando { param ( [string]$path, [string]$arguments, [string]$descripcion ) Write-Host "🔄…
-
Hi, agree with @Marc -Devoteam- you can use this trigger
-
Not sure if this is what you are looking for but I have this automation to add tagged users on comments as a request participants (request participants get notification when added) & maybe you can modify this to send a personalized email.
-
Hi, I did solve this issue using Forms. Here you got to the validation menu & set a limit.
-
You can list all your custom fields with this https://youworkspace.atlassian.net/rest/api/3/field
