Adding attachments to Scheduled Issues - workaround

From time to time we are receiving request about ability to add attachments to Scheduled Issues, we do not support this field for some reasons. One of them is that it's really risky to manage some data storage place where we would need to store attachments for the future usage. It's risky because we're not instance administrators and we cannot guarantee those attachments will live there and be available whenever they will be needed while creating an issue.

Here are few ideas that might help you to use attachment or attachments in scheduled issues. 

  1. If you need the same attachment in all of the Scheduled Issues:


    1. Use linking feature to SI with the issue including desired attachment:


      1. Linking issue in Scheduler wizard:




      2. After Execution of the Scheduled issue it will be linked to the issue with the file:




    2. Use direct links in the SI description:



      Description is up to you! So you can add direct links to needed attachment eg. Confluence pages / attachments, other Jira tickets / attachments or Google Drive files.


    3. If you are using images you can embed them into tickets with the use of '!' around the image url:





  2. If you need different files each time the Scheduled Issue is executed

    1. Editing scheduled issue, is not an option as editing SI through the wizard takes more steps to complete than adding an attachment to already created issue


    2. What you can do is leverage the power of predefined values in SI description!
      With predefined values you can create link that would change dynamically as the valued of variable changes, basically you should use those to change direct link to the file from 1.b and 1.c (examples above)

      Let's take look at first variable "${fireCount}" - it would change with each execution of Scheduled Issue and you can see current value in the table:



      1. You need to know the structure of the URL to know where to put the variable (below you will see the file list with the attachments used to create this example)
        First image link look like this: https://psc-software.atlassian.net/wiki/download/attachments/189333527/Screenshot_1.jpg?api=v2 
        Second image link: https://psc-software.atlassian.net/wiki/download/attachments/189333527/Screenshot_2.jpg?api=v2
        Third image link: https://psc-software.atlassian.net/wiki/download/attachments/189333527/Screenshot_3.jpg?api=v2
        It looks like the pattern is the same.


      2. After we trim the end, this would be our base attachment url: https://psc-software.atlassian.net/wiki/download/attachments/189333527/Screenshot_1.jpg


      3. Now we need to make it dynamic - change "1" into "${fireCount}": https://psc-software.atlassian.net/wiki/download/attachments/189333527/Screenshot_${fireCount}.jpg



      4. Seconds before first execution, take a look at the table it have '0' executions



      5. after successful issue creation



      6. next execution and result 



    3. You can experiment with available predefined values and formats/separators to match your file name needs.



Remember it is a part of the issue details, and this URL syntax depends on your configuration - make sure to test it and if the files are accessible to task assignee / end user



Won't do - possibly never.
The issue here is in storage of attachments, their availability and the usage.

  • If tasks are created on schedule in intervals, without editing it before creation of task... all would have same attachment - no point in keeping that attachment with template if its the same for all created issues - more effective is to keep it one place always available, even for changes in the attachment, then if you change it you don't need to change it in SI, because the link would be already correct eg. to some download section

  • If attachment needs to be different in each task, it is still better to update created issue than update template before every execution - there could be just a note (or subtask) in issue to add appropriate attachment

  • If it's a task for 1 issue which will be created in future only 1 time - again there is a storage problem, and the task should probably be created in Jira 'now', but with start date in future - because if you already have attachment for that task, looks like there is only need to set date when to start working on it.



Page attachments (feel free to test it with these screenshot links):



Related issues:

https://bitbucket.org/apdc/the-scheduler/issues/320/add-ability-to-attach-files-from-scheduled 

https://bitbucket.org/apdc/the-scheduler/issues/304/sugesstion-add-images-on-schedule-task-to

https://bitbucket.org/apdc/the-scheduler/issues/171/pictures-in-schedulded-issues-not

https://bitbucket.org/apdc/the-scheduler/issues/23/add-attachments-to-scheduled-issues