Tuncay Senturk _Snapbytes_ Community Champion

Hi @Berik Irgebayev You can schedule an automation rule to run weekly on a specific day, like Saturday, but there isn’t a built-in way to restrict it to a specific time window within that day (17:00 to 23:30). However, you can (to some extent) achieve this by combining a scheduled trigger with conditional checks within the…

You're very welcome!

Hi @SandeepSingh R In Atlassian Cloud products like Jira and Bitbucket, such as suspending or deleting users affect user access but do not result in the loss of data they have created.

You're welcome. I'm glad it worked.

Hello @Sia (Nastassia) Sharasheuskaya If you want to add the Confluence links to the channel description, you need to ensure that the purpose field in your JSON payload is formatted correctly and does not exceed Slack's character limit for channel descriptions. I see no problem in your json request but it's image, so let's…

Hello, I'm not sure if I got it correctly but here are the steps to check the completed status of a sprint in Jira Cloud. Navigate to your project and click on Reports. Then select Sprint Report from the options. In the Sprint Report, you can view all completed sprints and check their status, including which issues were…

Hi @Ha B_ the FIELD_LINK_TYPE parameter is used to specify the type of link to be created between the original and cloned issues, not to filter which existing links should be cloned. This is why specifying different link type IDs or names in FIELD_LINK_TYPE isn't working as you expected. Instead you can first Clone the…

Hi @Kruthika R Some required fields may not be filled. The best way to check is by clicking on the "executions have failed" link to see the reasons for the failures -if there are. You can also check application log files, I believe there should be something there.

Hello @Robin Lundberg The NullPointerException error is likely occurring because the requestType object is not being set correctly, which could be due to the fact that the issue is not fully created 'as you mentioned', and the Request Type field might not yet have the necessary data to return a valid object. the…

I quickly set up an Automation rule testing both escapeJson and replace functions. Both work well, I'd suggest escapeJson as it creates json friendly string for your web requests which may cause problems (e.g. escape " character which has a meaning in Json) However, I could not understand what is the issue in your case.…

Hi @Saravut Rangsunvigit I believe the problem might be related to authentication. As far as I know, Jira Cloud no longer supports basic authentication with passwords. Instead, it requires an API token. Changing the username might have invalidated existing sessions or credentials used by the plugin.

Are you certain that the custom field contains values for the issues? If it is empty or null, we may encounter an error, so it’s advisable to check if it has a value first. {{#if(issue.customfield_14408)}}{{issue.customfield_14408.replace("\n", "\\n")}}{{/}}

Also, I suggest you check the application logs; there may be information that helps us identify the issue.

Hi @Çağla Çebi I'm sorry to hear that you're experiencing this issue. The first thing that comes to my mind is that the Jira index might be corrupted, and boards might appear to be deleted when they are not. Have you reindexed Jira yet? If they are deleted and no data in the Audit logs, they may have been deleted directly…

I could not understand how it was unable to pull a value from the customfield? 

Hmm, let's try one more thing "incident_details": "{{issue.customfield_14408.replace('\n', '\\\\n')}}", or this "incident_details": "{{issue.customfield_14408.replace('\n', '\\n')}}", I apologize; I should have recreated the content and written it accordingly.

Oh, sorry! I was almost sure I had used it before, but I might be wrong.Could you try replacing \n characters as below? "incident_details": "{{issue.customfield_14408.replace("\n", "\\\\n")}}",

Hi @steven.allcock the newline characters (\n) in your custom field are causing the JSON to become invalid. You can use .escaprJson function to escape special characters like new line in you case {{issue.customfield_14408.escapeJson}} if it does not work you might want to escape characters by replacing them…

You're welcome!

Hi @Anna Rouhi It would be best to submit a ticket here. I'm sure they will respond as soon as possible.

You're welcome! I hope it helps

Hi @Mary from Planyway Swimlane configuration options can differ between project types. If you're using a Team-Managed project, some advanced board settings like swimlanes might not be available or are configured differently compared to Company-Managed projects. You can vote/watch this ticket.

Hi @Ken Zerkel Is this problem intermittent or still ongoing? Inspecting the history of these affected incidents could reveal what is causing them to appear. From the given input, I'd say that it sounds more like those old incidents are showing up because something is causing their date fields to update, making them appear…

Yes, as @[deleted] mentioned, it includes them. May 1, 2025, is a long time to change, though.

btw, I've managed to run a similar scenario

Time really does fly! Halloween is such a fun time of year. Glowsticks are a good idea, but they might ask, "OK, these are cool, but where are our candies?" 🎃 My favorite one is Reese’s Peanut Butter Cups. 

Did you try {{lookupIssues.components.name.flatten.unique}} while flatten breaks down arrays, unique will remove duplicates. Also did you try removing the == and use only one = "<my query> AND component = {{distinctComponent}}" I hope it helps

Hi @Afonso Souza After getting the author.accountId field in the Tempo API response, you can use the Jira REST API to retrieve user details based on this Account ID. The endpoint for this is: GET https://your-domain.atlassian.net/rest/api/3/user?accountId=<author.accountId> You can get user display name, avatar, etc using…

Hi @sammyl As you know the 422 error (Unprocessable Entity) means that the payload you are sending to the Jira REST API has problem(s), either because some required fields are missing or due to an invalid value. I see that you have already filled in the required message field. However, I recommend removing the optional…

Hi @Martin Hirsch As far as I know, using custom fields like Team as a condition for ending time in an SLA is not supported out of the box. There are a few workarounds you can consider: You can set up an automation rule that monitors changes to the Team field. When it changes, you can trigger a transition which will allow…