Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-14157

Allow for the creation of a issues in all projects of the instance

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Today, if there is a need to create an issue in every project of the instance it is necessary to have a separate action in the automation to each project:

      When working with multiple projects, making, maintaining, and documenting an automation rule like that can be laborious.

      The suggestion is to have an action that allows for creating an identical issue in all projects of the instance.

      In case there is anything stopping that (like the issue type missing in a project, or some conflict with mandatory fields) the rule could have it logged in its audit log.

        1. image-2023-03-13-14-48-51-933.png
          image-2023-03-13-14-48-51-933.png
          797 kB

            [JSDCLOUD-14157] Allow for the creation of a issues in all projects of the instance

            Ryan Pluckrose added a comment -

            Hi 

             

            Sorry, it seems my reply to Bill didn't send for some reason!

             

            This suggestion was raised from support from something I was asking.

             

            We use Jira Software for multiple projects  (more than 10) and each one has it's own sprint. We then have a central board where we can see the progress of all of them.

            We have quarterly and monthly maintenance tasks that take place and the detail on them will be the same across all projects, i wanted a way to create it once and then have it work for the projects I chose rather than create 10+ automation tasks. It also means that every time I need to udpate the task (i've done it a few times) I need to go into each one.

             

            It would also be good if the description used Rich Text as you can;t see what it will look like unless you run it.

             

            Sorry about the delayed reply.

            Ryan Pluckrose added a comment - Hi    Sorry, it seems my reply to Bill didn't send for some reason!   This suggestion was raised from support from something I was asking.   We use Jira Software for multiple projects  (more than 10) and each one has it's own sprint. We then have a central board where we can see the progress of all of them. We have quarterly and monthly maintenance tasks that take place and the detail on them will be the same across all projects, i wanted a way to create it once and then have it work for the projects I chose rather than create 10+ automation tasks. It also means that every time I need to udpate the task (i've done it a few times) I need to go into each one.   It would also be good if the description used Rich Text as you can;t see what it will look like unless you run it.   Sorry about the delayed reply.

            Charlie Gavey added a comment -

            This is supported today through Global Automation

            Charlie Gavey added a comment - This is supported today through Global Automation

            Bill Sheboy added a comment -

            What is the use case for this suggestion?  I could see this action causing challenges for individual team product owners/project admins by adding issues to their backlogs which they did not create/intake.

            Bill Sheboy added a comment - What is the use case for this suggestion?  I could see this action causing challenges for individual team product owners/project admins by adding issues to their backlogs which they did not create/intake.

              Unassigned Unassigned
              83c98eb92a41 eneis
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: