-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Atlassian Jira Audit Function Not Working #11362
Comments
Hi @macna, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
@macna, can you check for which columns the issue occurred by running the below parser - And please check the logs are received into the table |
@macna, Did you get a change to check on above comment? Thanks! |
Hi @macna, since we have not received a response in the last 5 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation. |
Hi @v-sudkharat apologies for the delay. The issue related to the EventCreationTime column, which doesn't seem to exist. Please reopen the issue. |
Hi @v-sudkharat - just to reiterate - can this issue be reopened, please? |
@macna , reopening the case. |
@macna, Please share the logs for - Jira_Audit_CL and Jira_Audit_v2_CL table to understand if the respective column has been created in the tables. |
Hi @v-sudkharat - I have reviewed this issue with my colleagues and have identified a misconfiguration on our part. Thanks for your help - closing. |
Describe the bug
The "JiraAudit" function included with the Atlassian Jira Audit solution throws the error "'project' operator: Failed to resolve scalar expression named 'EventCreationTime'"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Data to be returned using the column names defined in the function.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: