narrowizard opened a new issue, #4702: URL: https://github.com/apache/incubator-devlake/issues/4702
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened After the addition of the RemotelinkRepoPattern parameter to the Devlake Jira plugin (#4526), it was observed that using this parameter alone leads to an empty issue_repo_commits table. ### What do you expect to happen It is expected that RemotelinkRepoPattern should work alongside the existing RemotelinkCommitShaPattern parameter. Furthermore, it is expected that the data for creating the issue_repo_commits table should be sourced directly from the _tool_jira_remotelinks data rather than _tool_jira_issue_commits which currently uses the RemotelinkCommitShaPattern. ### How to reproduce In the devlake bp configuration, only set the RemotelinkRepoPattern parameter and do not set the RemotelinkCommitShaPattern parameter. Start devlake and sync jira data. Check the issue_repo_commits table in the database and find it empty. ### Anything else Recommended solution The _tool_jira_issue_commits logic should also utilize the RemotelinkCommitShaPattern parameter, or alternatively, the data for creating the issue_repo_commits table should be sourced directly from the _tool_jira_remotelinks. ### Version main ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
