Issue Summary

      Copying attachments from alerts to issues is not working using Automation with all triggers including manual

      Steps to Reproduce

      1. Create an automation in Operations using either alert triggers or manual triggers
      2. Add create issue action in automation and select copy attachments from trigger issue/current issue.

      Expected Results

      Attachments should be copied to the newly created issue

      Actual Results

      Issue is created but attachments are not copied

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [JSDCLOUD-15256] Copy attachment from Alert is not working

            Once again this bug was closed without resolution. This needs to be reopened. This is horrible customer service from Atlassian.

            Jonathan Boulgier added a comment - Once again this bug was closed without resolution. This needs to be reopened. This is horrible customer service from Atlassian.

            Hi a61164a3f06f ,

            I'm tempted to say someone hacked your account to make Atlassian look bad due to your response, which is absurd and not acceptable.

            The feature obviously exists and is supported since it's in automations. I included a screenshot of the feature, here's a screenshot again to refresh your memory:

            This ticket needs to be reopened again since it was not resolved. This is 100% a bug and needs to be resolved asap. Not to mention, this is basic functionality that Atlassian's competitors have had for over a decade. 

            Jonathan Boulgier added a comment - Hi a61164a3f06f , I'm tempted to say someone hacked your account to make Atlassian look bad due to your response, which is absurd and not acceptable. The feature obviously exists and is supported since it's in automations. I included a screenshot of the feature, here's a screenshot again to refresh your memory: This ticket needs to be reopened again since it was not resolved. This is 100% a bug and needs to be resolved asap. Not to mention, this is basic functionality that Atlassian's competitors have had for over a decade. 

            Currently we do not support copying attachments from alerts to issue which makes this not a bug but an expected behavior.

            Kumar Utkarsh added a comment - Currently we do not support copying attachments from alerts to issue which makes this not a bug but an expected behavior.

            HI 9acd6aeba90c and ebda5566d829 ,
            This is Utkarsh from the JSM-Automation team. Thanks for raising this ticket but I'd like to inform you that currently copying attachments from alerts to issues is not supported. Since this isn't supported, we can't accept this as a bug. However, you can go ahead and raise a feature request for this. Thanks!

            Kumar Utkarsh added a comment - HI 9acd6aeba90c and ebda5566d829 , This is Utkarsh from the JSM-Automation team. Thanks for raising this ticket but I'd like to inform you that currently copying attachments from alerts to issues is not supported. Since this isn't supported, we can't accept this as a bug. However, you can go ahead and raise a feature request for this. Thanks!

            You created an automation in a Project not in Alerts. Please see the steps to reproduce in the description of this ticket:

            1. Create an automation in Operations using either alert triggers or manual triggers
            2. Add create issue action in automation and select copy attachments from trigger issue/current issue.

            Jonathan Boulgier added a comment - You created an automation in a Project not in Alerts. Please see the steps to reproduce in the description of this ticket: Create an automation in Operations using either alert triggers or manual triggers Add create issue action in automation and select copy attachments from trigger issue/current issue.

            Hi ebda5566d829  and everyone,

            This is Rejaine from the Automation team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior within our instances. We would like to get to the root cause of what you’re experiencing.

            Could you provide some more details or a screenshot from the rules you created and was able to replicate the problem to help us narrow down this case?

            The screenshots below are example how we tried to replicate the rule you mentioned and the result after manual trigger was executed.

            Steps to Reproduce

            • Create a manual rule trigger
            • Add create issue action and select copy attachments from trigger issue/current issue

             

            Best,

            Rejaine Lima.

            Rejaine Lima added a comment - Hi ebda5566d829   and everyone, This is Rejaine from the Automation team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot from the rules you created and was able to replicate the problem to help us narrow down this case? The screenshots below are example how we tried to replicate the rule you mentioned and the result after manual trigger was executed. Steps to Reproduce Create a manual rule trigger Add create issue action and select copy attachments from trigger issue/current issue   Best, Rejaine Lima.

            Hi Johnathan, my sincere apologies for this, I seem to have accidentally responded to the wrong ticket.

            Hwee Sen Wee added a comment - Hi Johnathan, my sincere apologies for this, I seem to have accidentally responded to the wrong ticket.

            This ticket has been marked as fixed but is not fixed. Why was it closed??

            Jonathan Boulgier added a comment - This ticket has been marked as fixed but is not fixed. Why was it closed??

            Cheers Corey, thanks for the confirmation

            Hwee Sen Wee added a comment - Cheers Corey, thanks for the confirmation

              36bd3fea80e3 Makarand Gomashe
              ebda5566d829 Mikhael Markov
              Affected customers:
              2 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: