Tuncay Senturk _Snapbytes_ Community Champion

Hi @Priya ThirumalaiKrishnamoorth Without seeing the script, it's difficult to determine what the problem is. However, the error message "null value in entry" indicates that you need to have some null checks. I would recommend doing so, as well as adding more debug logs to understand better what is happening with the…

You're very welcome!

Hi @Cedacri You're absolutely right that the listener executes too fast before Jira fully indexes the newly created subtask. Please take it with a pinch of salt, as far as I know, in Jira, listeners execute before the transaction is committed meaning that indexing has not yet taken place when your listener runs. This is…

This is a very old post, and I am not sure if you have already found a solution. Out of the box, you cannot define such a complex round-robin assignment; however, there is a free app called SnapAssign that enables you to achieve this. You can define as many rules as well as shifts (in different timezones with different…

Hmm, that's weird, seems like Groovy interpreter does not accept break inside the switch. Anyway, I'll rewrite the script without break statements. def issueKey = issue.key def TCName = 'Technical Certainty' def DCName = 'Definition Certainty' def CLField = 'Confidence Level' def TCValueObj =…

Wow! Time flies; it feels like just yesterday when I was in Vegas for Team '24, and now you're saying it's only 47 days away for Team '25. I haven't registered yet. The flight to the US is becoming more of a hassle, which makes me feel like I'm getting old. So far, I’d say there’s a 49% chance I’ll be there and a 51%…

Hi @Alby Siby Have you checked the log file already which is located in <JIRA_HOME>/log/atlassian-jira.log file? You should have more information there.

It's quite difficult to identify the issue without any error traces; however, if you're certain that there are no error logs in the log file related to this problem, you should be able to find something in the browser console logs. Have you checked those already? You can also trace the problem by commenting out larger…

Hi @giridharan Have you checked the Jira logs to see if any errors are preventing the UI from loading? You can see the logs in <JIRA_HOME>/log/atlassian-jira.log file There should be something preventing Jira from being up and running normally and the devil should be in the logs.

Hi @Mohan R This is the Atlassian Community site, where users help each other with discussions and best practices. I recommend raising a support ticket with Atlassian directly via Atlassian Support. That way, the Atlassian team can review your request and provide guidance or consider improvements for future updates.

Hi @Cristy Flaherty getCustomFieldValue returns more than just the value of the dropdown fields, it returns an JSON string including the id, value and the self calling URL. This is very expected behavior. You need to modify your script to extract the wanted values. Could you try the below code? (I've modified more as there…

Hi @Ann It is quite challenging to say anything based solely on this log. If it only appears during startup and does not cause any functional issues, I would recommend ignoring it, as it may be initialising an integration. However, if this occurs more frequently, the context and the logs preceding or following will be…

I’ve never been great with special days or buying gifts, but luckily, my wife was away with the kids for half-term—so I made the most of it by treating myself to a solo pub night with some good beers. Cheers to self-love! 🍻 😆

Hi @Jens Bode That's strange. Have you checked the workflow for the Task issue type? Confirm that the workflow appears correct and the statuses are accurately mapped. While this isn't expected behaviour, it’s possible that the statuses may have been deleted or corrupted (take this with a pinch of salt please, I am just…

Hi @Emilia KASPRZYK You can configure multiple SLAs for different issue types and handling teams based on issue statuses and other conditions. Go to Project settings > SLAs and Add SLA, then define your SLA#1 for Team #1 - Start: When the issue enters the first relevant status (e.g. "Waiting for Support") - Stop: When the…

Hi @Karmandroid Singularity, I think there is a workaround to sort the resolution field options in a workflow transition. You can use a workflow property for the transition for which you wish to change the order. In this article, you will find the properties outlined. You can use the jira.field.resolution.include property…

Hi @lei It has been so long but I remember I managed to use AOP in a Jira plugin by the help of this article. https://community.atlassian.com/t5/Jira-articles/Spring-Java-based-configuration-and-AOP-in-Jira-plugins/ba-p/762265 It's a quite old article but it may shed a light, hopefully.

Hi @Tatiana Marti Unfortunately, Jira JQL does not support dynamic date calculations natively (in your case, based on a fix version's release date) natively. You can either use a custom field which will be automatically set (with Automation) and use this date in your JQL, or use ScriptRunner's issuefunction in dateCompare…

You're welcome!

Yes, you can detect if a user was deleted (or deactivated) via the Jira REST API. However, I'm uncertain whether you can differentiate between the two; I mean, I don't know if there is a way to determine if the user is deactivated due to being deleted. You can call /rest/api/3/user?accountId=<USER_ACCOUNT_ID> REST API and…

Hi @Vasilis Kokotakis Take it with a pinch of salt but I presume, when a user is deleted in Jira, their account is deactivated but not removed entirely. In order to retain historical data related to the user (they created, commented, transitioned, etc) this is a must for the auditing and issue history purposes.

Okay, what about the logs? Did you notice that the error related to gson has disappeared? I just want to rule that out before moving on to the other error logs in your log file.

Hi @Shubham Sharma It is very difficult to find the root cause, but it is best to clear the problems in the logs, as the devil is in the logs. For instance, one of the errors in the log "Could not load [com.google.gson.GsonBuilder]" suggests a dependency issue, with Gson. Have you already had a dependency with Gson…

Hi @COORDINADOR MUTUALIA The image you shared is too small to identify the problem. In the Create Subtask action, store the created subtask in a smart value variable {{createdIssue}} and use that in the assignment action so that rule assigns the subtask instead of the original task (main issue). So, instead of issue use…

Not the default filter but you can change the order and drag the filter to the top. SImilarly you can do the same for JSM queues.

Hi @Rohan Shastri I don't think the REST call to /rest/api/4=3/user/search would return the details of the created issue; there must be some mistakes in your configuration. Try testing the API in Postman or using curl (or a browser) to ensure the expected response is returned, then use it in your automation rule. I would…

Hi @Ansu Sabu Sorry if I got it wrong but, you can add below JQL to your filter to exclude subtasks issuetype NOT IN subTaskIssueTypes() then if you make that filter as the default filter, that would work.

I don't believe this is the most effective way to achieve this. I mean, you need to use a regular expression to parse the entire description field, select the relevant parts, and perform the calculations. This is not particularly difficult, but it is quite error-prone. There may be other dates and time indicators; how will…

Hi @Mohamed Eid Could you elaborate further on the problem you wish to solve? You have both the start date and the remaining days in the issue's description field, and you want to perform a calculation to determine the expiry date; is that correct? The description field is a text field and can contain a lot of free-format…

This was my favorite!