You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's going to depend on the Jira webhook automation.
Moreover, we can receive the comment events from Gitlab but I don't think it's possible to link that with an existing Jira issue unless we include the Jira issue id upon creation somewhere on the Gitlab issue (labels?) that we would then have to parse out from the incoming webhook.
There is the possibility of creating a new Jira automation to send a webhook upon ticket creation where we can use Gitlab issue labels to store the Jira ticket ID but we would then have to include functionality on the yaml templating to iterate all the labels and pick the right one with the Jira ticket ID. That's pretty far fetched to me.
There is the possibility of creating a new Jira automation to send a webhook upon ticket creation where we can use Gitlab issue labels to store the Jira ticket ID but we would then have to include functionality on the yaml templating to iterate all the labels and pick the right one with the Jira ticket ID. That's pretty far fetched to me.
That's fair. Inside the repo settings of Gitlab webhooks there's an additional checkbox for Issue Comments (we just have Issue Events selected) for the payload. It could be that Issue Events including updated will do this anyway.
Beyond just creating issues via the Gitlab webhook "Issue Events" webhook category we should also look to support additional payloads like
A comment is added to an issue or merge request
An issue is created, updated, closed, or reopened.
Right now transformers work for when an issue is created.
The text was updated successfully, but these errors were encountered: