Tuncay Senturk _Snapbytes_ Community Champion

Well done @Monique van den Berg and team 👏👏👏

Thanks everyone for sharing your experiences and perspectives.

Hi @Jade Zavitoski What you're seeing looks like expected behavior, not a bug Workforce automatic routing is designed for new work items at initial routing time. Atlassian's docs describe it as picking an agent when a new item comes in with a team assigned, there's no mechanism to re-evaluate routing when the Team field…

Hi @Michail Kotantakis The API documented here shows that there are three parameters (offset, size and targetAccountId. So use GET for the below endpoint https://api.atlassian.com/jsm/ops/api/{cloudId}/v1/users/contacts?targetAccountId={accountId} To retrieve all users’ contacts, you would need to first get the relevant…

Hi @Sathish Kumar Native JQL can’t filter by comment author or comment date, comments aren’t indexed as JQL fields. Tricks like updated >= -24h catch all issue changes, not just comments. For a dashboard widget (Filter Results gadget + saved filter), you need extended JQL. There are some JQL apps on the market, you can use…

Thank you so much for the kind words. The Community has been a huge part of my journey, both personally and professionally. Grateful to everyone I’ve interacted with along the way 🙏

Hi @Aditya Hosamani When you complete a sprint, Jira automatically moves incomplete issues to the next sprint (or backlog) and treats Resolved/Done issues as completed work, regardless of what sprint they’re assigned to. Because of this, a ticket in resolved category is considered completed in the sprint, so it is removed…

Hi @Bernhard Mostrey I am not sure if you've already found the answer to this. The json tells that the attachment is referenced incorrectly (type: external) in the comment body. This does not work properly in the JSM portal. I do not know which/how you used REST API below are the correct API endpoints for uploading the…

Hi @Yugandhar Bandi The error is caused by the function parameter NextPageToken with a variable of the same name inside the let block. You redefined a variable with the same name as a parameter. use a different variable name instead of redefining NextPageToken. ReturnedNextToken = try Source[nextPageToken] otherwise null

Hi @Sandra Herlufsen Sorry for the late response, I am unsure if you already found the solution for this. This 403 error message usually indicates that the request being executed by the provider is hitting a Teams API endpoint internally. As you suspected, some endpoints resolve additional team metadata during the read…

Hi @Marc Tseu Did you have a chance to find a solution for this?

Hi @Mary Doherty For Company-managed projects, Jira has built in solution: Control chart (Board -> Reports -> Control Chart) It automatically calculates cycle time, showing how long issues stayed between the first "In progress" status and the last "Done" status. It also provides the average cycle time and shows each issue…

Hi @Goutam Singla This addon is designed to be used via Storybook configuration, not by manually importing decorators. You should register/inject it in .storybook/main.ts export default { addons: ['@atlaskit/storybook-addon-design-system'], }; If you need a design token decorator, instead of using withDesignTokens, use the…

Hi @Michelle Kirk @Rilwan Ahmed is right, delegation is not a Jira builtin feature. Jira Automation can handle basic round-robin or balanced workload assignment, but it doesn’t provide a clean way to dynamically exclude users (e.g. sick leave, holiday, training) without manually editing the rule each time. If you’re…

Hi @Rosalin kandapan That's a good and tough question, but here is my two cents on this. Please take it with a pinch of salt. In the list view, Jira shows the stored field value. For a Forge custom field, that's what you saved (like JAP-218: Epic D). When the epic's summary changes, Jira does not re-compute other issues'…

Hi @Oleh Kosar Unfortunately, you can’t call a Forge resolver from an adopted connectModules page. invoke() only works when your frontend is running inside a Forge UI runtime. However, the best place to ask developer questions is the Atlassian Developer Community.

Hi @Cory Boslet I know it's frustrating, and this is what we face regularly, things broke all of a sudden. Anyway this narrows the problem (hopefully): Either it's not running with the sal-api jar you think you are (even if Gradle shows it in the graph) or the sal-api jar you have on disk is not the real…

Hi @Cory Boslet com.atlassian.sal.api.executor.ThreadLocalContextManager is in Atlassian SAL, and the error says that your runtime classpath contains a missing or an older sal-api.jar The JRJC core module depends on com.atlassian.sal:sal-api and for the JRJC 5.2 the dependency should be sap-api:3.0.7 I don't know why it…

Hi @Fabian As far as I remember in batched notifications, it is not rendered with an $issue in the velocity context. So it always returns null. You will need to fetch the issue and get the customfield value from the issue which may not be the most performant way. I am not 100% sure but I think you can get the issuekey from…

Hello @Nikola Perisic Have you found a solution for this? If you elaborate, we may help.

Hello @Varvara K_ While (as @Deivid Araujo ,it's technically possible with Automation, it quickly becomes complex (multiple rules, manual field toggles, fragile logic). That's why our team implemented SnapAssign – Smart Assignments for Jira. You can set up working hours, shifts, holidays and all work according to the…

No problem! Happy to help!

Hi @Patrick Schneider I think Stagil tables don't write cell diffs into Jira's native issue changelog. So you'll need to use their REST API and use the response inside Automation. Checking their documentation, you can use the below REST service GET…

When your Assets attribute contains more than 1 user, Automation treats it like a list, so: {{object."Patchverantwortlicher".get(0)...}} works But when it contains exactly 1 user, it treats it like a single object (not a list). so .get(0) fails. You can try using asList.first as the below. I am not sure if it will work but…

Sorry but when I read my comment after submitting, I wanted to add this, the quickest proof * temporarily remove all top-level conditions * in each branch, keep only: For AQL Lookup work items If {{lookupIssues.size}} = 0 Create issue Manually run the rule once. If it still doesn’t create issues, add a Log action inside…

Thanks for the screenshots, It's a tough one. From your screenshots, I want to make sure: your compare two values condition on the date may block the whole run, In your earlier setup you had conditions like: {{now.day}} > 7 and {{now.day}} < 15. And your audit shows runs on 15th , so the {{now.day}} < 15 condition is…

Hi @Antonia Your two AQL branches are right, but the lookup + create issue block in Group 3 is in the wrong place. Everything inside a For AQL branch runs once for each matching asset. As soon as the branch ends, the rule context goes back to the trigger. So, in your current rule, branch 1 finds objects with typeId 194 but…

Hi @Antonia As far as I understand, you created a rule per object type with id = 194 (server). If so, yes, the rule scope is one object type and it does not include the id = 236 (virtuelle server). So, because the automation context is tied to one object type, you can't combine 194 and 236 in a single AQL branch. I assume…

Hi @Vignesh G You can get the full history on the issue response (along with the jira fields) using the expand parameter. GET /rest/api/3/issue/${issueIdOrKey}?fields=${fields}&expand=changelog If you just need the history for one issue together with some fields, use .GET /rest/api/3/issue/{issueIdOrKey}?expand=changelog…

Hi @G P N Jira does not support conditions directly on post-functions. I think you are using a Deviniti app and to add user to an AD group. If Deviniti's post-function doesn’t include its own conditional execution, then it will always run. I think it would be best to contact Deviniti's support to see if they can add a…