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

Ability to make Jira 'read only'

XMLWordPrintable

    • 186
    • 53
    • Hide
      Atlassian Update – 8th February 2018

      Hi Everyone,

      Thanks for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

      This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 8th February 2018 Hi Everyone, Thanks for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Kind regards, Jira Server Product Management
    • 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.

      When performing an upgrade, it would be nice to be able to put Jira into read-only mode. It takes a long time (10-15m) for the XML import to run now so currently this is downtime for the users because we have to shut down the existing instance. If we could put the existing instance into read-only mode, then run up the new installation, import the data and then switch, we could have an (almost) completely seamless upgrade.

      – Michael Brown

          Form Name

            [JRASERVER-1924] Ability to make Jira 'read only'

            Malka Jackson [Isos Technology] added a comment -

            We have this feature for Confluence spaces now, why the holdup for Jira? My current migration Client has 1200 projects (let's not talk about their governance issues.) and to manually set each project to a new permission scheme takes way too long which causes a delay before they can reopen the source instance in read-only to allow their users to compare the migrated data to original data.

            Malka Jackson [Isos Technology] added a comment - We have this feature for Confluence spaces now, why the holdup for Jira? My current migration Client has 1200 projects (let's not talk about their governance issues.) and to manually set each project to a new permission scheme takes way too long which causes a delay before they can reopen the source instance in read-only to allow their users to compare the migrated data to original data.

            Dariusz PAWLAK added a comment -

            This is a very useful feature.

            Dariusz PAWLAK added a comment - This is a very useful feature.

            David Pearce added a comment -

            This is something I really need for  the migration I am doing. Please consider implementing this feature.

            David Pearce added a comment - This is something I really need for  the migration I am doing. Please consider implementing this feature.

            bilel.arfaoui added a comment -

            I think this is a crucial feature for clients migrating from server to cloud/DC, but now server has reached it's EOF and still no news...

            bilel.arfaoui added a comment - I think this is a crucial feature for clients migrating from server to cloud/DC, but now server has reached it's EOF and still no news...

            Jeramy added a comment -

            This is sad.

            Atlassian...if you're not going to give us a feature after 19 years, at least have the courtesy to at least close this issue and give us a reason why.

            Jeramy added a comment - This is sad. Atlassian...if you're not going to give us a feature after 19 years, at least have the courtesy to at least close this issue and give us a reason why.

            William Hogg added a comment -

            This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

            Well its been a lot more than 12 months....

            William Hogg added a comment - This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. Well its been a lot more than 12 months....

            Alex Janes added a comment -

            We really need this. If I want to update an addon, it can sometimes affect workflows and other functionality. Especially if I am updating ScriptRunner.

            Being able to lock everyone out of Jira while I do that would be 100x better than just clicking update and praying no one was doing anything.

            Alex Janes added a comment - We really need this. If I want to update an addon, it can sometimes affect workflows and other functionality. Especially if I am updating ScriptRunner. Being able to lock everyone out of Jira while I do that would be 100x better than just clicking update and praying no one was doing anything.

            Trevan Householder_Isos-Tech-Consulting_ added a comment - - edited

            Agree 100% @casper. This continues to be an ongoing need. As an Atlassian partner who performs multiple migrations for Atlassian customers per month, this functionality would be used frequently, and would provide a better experience for customers in the migration process.

            Atlassian, here's a way to make the migration from ground to cloud easier.

            Trevan Householder_Isos-Tech-Consulting_ added a comment - - edited Agree 100% @casper. This continues to be an ongoing need. As an Atlassian partner who performs multiple migrations for Atlassian customers per month, this functionality would be used frequently, and would provide a better experience for customers in the migration process. Atlassian, here's a way to make the migration from ground to cloud easier.

            Casper Hjorth Christensen added a comment -

            Would be great to be able to set Jira into a read-only mode, prior to migration from Server/DC to Cloud.

            This would be most useful when "Site Export/Import" is used, to ensure that no new tickets/requests/issues are created while the XML Export is running.

            Casper Hjorth Christensen added a comment - Would be great to be able to set Jira into a read-only mode, prior to migration from Server/DC to Cloud. This would be most useful when "Site Export/Import" is used, to ensure that no new tickets/requests/issues are created while the XML Export is running.

            john.cougar added a comment -

            So ... any progress on this issue? A maintenance mode for Jira and Confluence seem like mandatory features to a lot of your administrative user base. Do you have suggested workarounds? Has anything happened to enable a solution to this idea?

            john.cougar added a comment - So ... any progress on this issue? A maintenance mode for Jira and Confluence seem like mandatory features to a lot of your administrative user base. Do you have suggested workarounds? Has anything happened to enable a solution to this idea?

              Unassigned Unassigned
              dave@atlassian.com dave (Inactive)
              Votes:
              472 Vote for this issue
              Watchers:
              270 Start watching this issue

                Created:
                Updated: