• Type: Bug
• Resolution: Unresolved
• Priority: Low
• Component/s: Trigger - Other
• Labels:

  • jsw-s13

1. 

   image-2025-01-08-11-22-10-266.png

   27 kB

   08/Jan/2025 12:22 AM

2. 

   image-2025-01-08-11-22-22-476.png

   36 kB

   08/Jan/2025 12:22 AM

[AUTO-1642] Deployment successful trigger displays warning despite integration with Bitbucket

Alicia Hadisaputra made changes - 08/Jan/2025 12:40 AM

Description

Original: h3. Issue Summary Deployment successful trigger displays a warning _"Connect a deployment tool to use this trigger"_ despite of having deployment set up with bitbucket. Despite of the warning, the rule is executing successfully.  h3. Steps to Reproduce  # [Integrate Bitbucket with Jira|https://support.atlassian.com/jira-cloud-administration/docs/integrate-bitbucket-with-jira/]   # [Set up deployment integration|https://support.atlassian.com/jira-cloud-administration/docs/set-up-your-deployment-integration/]  # Create a rule in the same project with "deployment successful trigger"  # Trigger the rule by deploying a commit with issue key   # Observe _releases_ field in the commited issue and the automation tab showing recent rule runs  h3. Expected Results !image-2025-01-08-11-22-10-266.png! h3. Actual Results !image-2025-01-08-11-22-22-476.png! h3. Workaround Currently there is no known workaround for this behaviour. A workaround will be added here when available

New: h3. Issue Summary Deployment successful trigger displays a warning _"Connect a deployment tool to use this trigger"_ despite of having deployment set up with bitbucket. Despite of the warning, the rule is executing successfully.  h3. Steps to Reproduce  # [Integrate Bitbucket with Jira|https://support.atlassian.com/jira-cloud-administration/docs/integrate-bitbucket-with-jira/]   # [Set up deployment integration|https://support.atlassian.com/jira-cloud-administration/docs/set-up-your-deployment-integration/]  # Create a rule in the same project with "deployment successful trigger" h3. Expected Results !image-2025-01-08-11-22-10-266.png! h3. Actual Results !image-2025-01-08-11-22-22-476.png! h3. Workaround Currently there is no known workaround for this behaviour. A workaround will be added here when available

Alicia Hadisaputra made changes - 08/Jan/2025 12:30 AM

Was this caused by a recent change?		New: Yes, existing functionality was broken by another team [ 19031 ]
Status	Original: Needs Triage [ 10030 ]	New: Gathering Impact [ 12072 ]

jhaloot made changes - 08/Jan/2025 12:25 AM

Labels

New: jsw-s13

Alicia Hadisaputra created issue - 08/Jan/2025 12:25 AM