Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-28268

Provide administrators the ability to disable or default autowatch

    • 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.

      Atlassian status as of 23rd November, 2012

      Hello All,

      Thanks for all your votes and comments.

      We are beginning to investigate a workable solution for an autowatch setting for JIRA administrators. At this stage we hope to get it into a 5.2.x release, but we can not guarantee that right now.

      We will update this issue as more information comes to hand.

      Cheers,

      Roy Krishna
      JIRA Product Management

            [JRASERVER-28268] Provide administrators the ability to disable or default autowatch

            Terry Beavers added a comment - - edited

            I think I may be blind.

            Does anyone know how to change the global default Autowatch setting in JIRA Software 7.0?

            Thanks,

            Terry

            UPDATE: never mind, found it!

            Terry Beavers added a comment - - edited I think I may be blind. Does anyone know how to change the global default Autowatch setting in JIRA Software 7.0? Thanks, Terry UPDATE: never mind, found it!

            I like it. "Default autowatch" (lower case a to match the others on that screen).

            Eric Dalgliesh added a comment - I like it. "Default autowatch" (lower case a to match the others on that screen).

            Why don't we just call it 'Default Autowatch' ?

            Roy Krishna (Inactive) added a comment - Why don't we just call it 'Default Autowatch' ?

            We're going with "Users who create or comment on issues will automatically watch those issues."

            Eric Dalgliesh added a comment - We're going with "Users who create or comment on issues will automatically watch those issues."

            'gg' - no.

            However the current label for this is far too verbose:
            "Users who create or comment on an issue will automatically be watching for future changes to this issue."

            Please change that to something more simple.

            Roy Krishna (Inactive) added a comment - 'gg' - no. However the current label for this is far too verbose: "Users who create or comment on an issue will automatically be watching for future changes to this issue." Please change that to something more simple.

            Do we need a separate issue for gg for autowatch, should we hold up the feature for it, or should we ship without it and not ever ship it? My personal opinion is we can ship without it working with gg because it's not the sort of thing we expect people to change a lot. I don't think we need to ever add it.

            Eric Dalgliesh added a comment - Do we need a separate issue for gg for autowatch, should we hold up the feature for it, or should we ship without it and not ever ship it? My personal opinion is we can ship without it working with gg because it's not the sort of thing we expect people to change a lot. I don't think we need to ever add it.

            Testing observations

            Discoverability may be an issue (no gg shortcut for autowatch) - it's under User Preferences which is the right place for it
            Websudo is respected
            If the user profile for autowatch is "Inherit from global settings" then changing to disabled in user preferences is applied to all future issues created
            Changing from enabled to disabled and vice versa does not alter existing issue watch lists.
            On upgrade the default user behaviour is "Inherit from Global Settings" if the user has not explicitly changed it
            If a user has changed to disabled, it is still disabled on upgrade
            New users default to "Inherit from Global Settings"

            tier-0 grump added a comment - Testing observations Discoverability may be an issue (no gg shortcut for autowatch) - it's under User Preferences which is the right place for it Websudo is respected If the user profile for autowatch is "Inherit from global settings" then changing to disabled in user preferences is applied to all future issues created Changing from enabled to disabled and vice versa does not alter existing issue watch lists. On upgrade the default user behaviour is "Inherit from Global Settings" if the user has not explicitly changed it If a user has changed to disabled, it is still disabled on upgrade New users default to "Inherit from Global Settings"

            Alvis Yeo added a comment -

            kudos to Atlassian for noting the critically of this FUG. thanks.

            Alvis Yeo added a comment - kudos to Atlassian for noting the critically of this FUG. thanks.

            And there's no plan to enable Administrators to completely disable autowatch? By my reading, that's still a (big) requirement for more than a few people who have participated on this issue. The Admin options should be between "off", "autowatch" and "don't autowatch".

            Mike Curwen added a comment - And there's no plan to enable Administrators to completely disable autowatch? By my reading, that's still a (big) requirement for more than a few people who have participated on this issue. The Admin options should be between "off", "autowatch" and "don't autowatch".

            We're currently targeting this at 5.2.2. Whether it makes that release or a later one depends on a few factors.

            The current plan is to make it so that, after upgrading, people who have explicitly set their preference will retain that preference, but other users will use the default. Administrators will be able to change the default, which will be reflected in the notification behaviour of anybody without an explicit preference. Users will be able to manage what their preference is from the options autowatch, don't autowatch, and default.

            Eric Dalgliesh added a comment - We're currently targeting this at 5.2.2. Whether it makes that release or a later one depends on a few factors. The current plan is to make it so that, after upgrading, people who have explicitly set their preference will retain that preference, but other users will use the default. Administrators will be able to change the default, which will be reflected in the notification behaviour of anybody without an explicit preference. Users will be able to manage what their preference is from the options autowatch, don't autowatch, and default.

              edalgliesh Eric Dalgliesh
              shaldane Sam Haldane (Inactive)
              Votes:
              109 Vote for this issue
              Watchers:
              84 Start watching this issue

                Created:
                Updated:
                Resolved: