• Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      It would be nice with a function for assigning a notification scheme to several projects in the same operation. (As described in JRA-4505 this could also be interesting to other sheme types as well.)

      We have lots of JIRA projects and several notification schemes. Each time we take the production database and lift it over to our test system we have to disable notifications. As I understand it - and i have consulted the documentation - I have to make lots of operations i.e. disable notification for all projects one by one. Or change several notification schemes (and that is just as tedious).

      I suggest that on the Notification scheme screne - you introduce a new screen where I can fill in with a checkbox for each project and then select any notificatin scheme - including "None" of course.

      And why not doing this for other schemes as well. (see JRA-4505)

      As proposed in JRA-4505 this might be done for all projects that belongs to the same category but I want also that it shall be possible to select from the whole project list.

            [JRASERVER-28833] Project bulk scheme change

            Joining to it's good to have.

            Ivan Donigevich added a comment - Joining to it's good to have.

            I agree with Marc K Watkins. Administrators should be able to bulk change project schemes, especially notification schemes. That is crucial for maintaining a Jira instance, both sandbox and production.

            Linera Abieva added a comment - I agree with Marc K Watkins. Administrators should be able to bulk change project schemes, especially notification schemes. That is crucial for maintaining a Jira instance, both sandbox and production.

            MarcW added a comment -

            Disabling the e-mail server is not a good solution for this case. I too have the same problem with our sandbox environment. I need the e-mail server up and running so I can test add-ons and other functionality, but I do not want notifications sent out every time I play with the data.

            Having some way to quickly mass change notification schemes on a project level would be invaluable.

            MarcW added a comment - Disabling the e-mail server is not a good solution for this case. I too have the same problem with our sandbox environment. I need the e-mail server up and running so I can test add-ons and other functionality, but I do not want notifications sent out every time I play with the data. Having some way to quickly mass change notification schemes on a project level would be invaluable.

            Hi Rolf,

            Many thanks for your suggestions.

            We do plan to make some changes in this area in the near future, however it most likely wont include a project bulk scheme change.

            Also I'll just quickly mention that when we move our production server to a test environment, we don't change every notification scheme. We simply disable the outgoing mail server settings in JIRA. Hopefully that works for you too.

            Cheers,
            Roy

            Roy Krishna (Inactive) added a comment - Hi Rolf, Many thanks for your suggestions. We do plan to make some changes in this area in the near future, however it most likely wont include a project bulk scheme change. Also I'll just quickly mention that when we move our production server to a test environment, we don't change every notification scheme. We simply disable the outgoing mail server settings in JIRA. Hopefully that works for you too. Cheers, Roy

              Unassigned Unassigned
              71e22d6b061d Rolf Mellberg
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: