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

      Next-gen projects and their features, like the Roadmap, are only currently available in Jira Cloud. It'd be a welcome addition to Server and Data Center distributions.

          Form Name

            [JRASERVER-68153] Release next-gen projects in Jira Server

            When this will be fixed, we need plenty of next-gen project that need to be imported on data center edition?

            Vinoth Faraday PS added a comment - When this will be fixed, we need plenty of next-gen project that need to be imported on data center edition?

            @79515d73f28b could you please comment why? Thanks!

            Petr Plenkov added a comment - @79515d73f28b could you please comment why? Thanks!

            I'm actually very happy for the first time that Atlassian is not implementing a feature , keep this away from DC please and never implement this feature.

            Martin Kottisse added a comment - I'm actually very happy for the first time that Atlassian is not implementing a feature , keep this away from DC please and never implement this feature.

            We need Next-Gen projects in our Data Center. Many users are asking for it. We cannot move to cloud due to "local" regulations....  Making this available in Data Center should be an easy job. 

            Jan Erik Musiol added a comment - We need Next-Gen projects in our Data Center. Many users are asking for it. We cannot move to cloud due to "local" regulations....  Making this available in Data Center should be an easy job. 

            Marcel Sottnik added a comment - - edited

            I feel really betrayed as a small company not willing to go all "let's forget privacy" way. I can only reiterate once again I was a big fan of Jira and later Confluence/Fisheye/Bitbucket since 2007. I implemented and/or recommended it to multiple smaller or bigger companies. Now I am dropping out of the whole Atlassian infrastructure and I am advising the same to anyone concerned.

            Marcel Sottnik added a comment - - edited I feel really betrayed as a small company not willing to go all "let's forget privacy" way. I can only reiterate once again I was a big fan of Jira and later Confluence/Fisheye/Bitbucket since 2007. I implemented and/or recommended it to multiple smaller or bigger companies. Now I am dropping out of the whole Atlassian infrastructure and I am advising the same to anyone concerned.

            I don't think this request will go away

            [Future server pricing overview & FAQs | Atlassian|https://www.atlassian.com/licensing/future-pricing/server-pricing/faqs]
            Important changes to our server and Data Center products
            We’re making changes to our server and Data Center products, including the end of sale for new server licenses on February 2, 2021 and the end of support for server on February 2, 2024. Learn what this means for you.

            victorgonzales added a comment - I don't think this request will go away [Future server pricing overview & FAQs | Atlassian|https://www.atlassian.com/licensing/future-pricing/server-pricing/faqs] Important changes to our server and Data Center products We’re making changes to our server and Data Center products, including the end of sale for new server licenses on February 2, 2021 and the end of support for server on February 2, 2024.  Learn what this means for you.

            Really disappointed with this decision. To them, we might be just a small number behind DC and Cloud prospect. So we just go anywhere else if we can. They don't really care much, I believe.

            I'm going to drop out of this ticket from now on. It's useless to vote.

            Hung Nguyen added a comment - Really disappointed with this decision. To them, we might be just a small number behind DC and Cloud prospect. So we just go anywhere else if we can. They don't really care much, I believe. I'm going to drop out of this ticket from now on. It's useless to vote.

            dchisholm added a comment -

            Imagine how many Jira Server comments would be up-voted since the announcement if Jira supported comment voting.  I've yet to see any comment saying something like "Finally - now I have the justification to move my company's on-prem Jira to Cloud.  It's what I wanted for so long."

            And does anyone has faith that Atlassian will continue to support Data Center once they have a FedRAMP ATO?  The DoD uses Jira extensively, and I'm sure they'll jump to a FedRAMP environment when it's available.  With that huge customer base moved off DC, I expect Atlassian to deprecate DC soon after.

            For me, my search for a replacement officially starts this week.  Where's that youtrack importer?  Ah, there it is - https://www.jetbrains.com/help/youtrack/standalone/importing-from-jira.html.

             

             

            dchisholm added a comment - Imagine how many Jira Server comments would be up-voted since the announcement if Jira supported comment voting.  I've yet to see any comment saying something like "Finally - now I have the justification to move my company's on-prem Jira to Cloud.  It's what I wanted for so long." And does anyone has faith that Atlassian will continue to support Data Center once they have a FedRAMP ATO?  The DoD uses Jira extensively, and I'm sure they'll jump to a FedRAMP environment when it's available.  With that huge customer base moved off DC, I expect Atlassian to deprecate DC soon after. For me, my search for a replacement officially starts this week.  Where's that youtrack importer?  Ah, there it is -  https://www.jetbrains.com/help/youtrack/standalone/importing-from-jira.html .    

            William Roush added a comment - - edited

            Hey Nick Dring, just in general we had a few major gripes, we don't use DC though so we can't speak on the side of that.

            • The new UI is a step down for a lot of us, being forced into it with no choice was annoying (yeah I know this can be the case with all UI changes but there is a reason a lot of people prefer things like Github to Bitbucket, don't follow Bitbucket's annoying UI)
            • We always had worse performance, we give a nice bit of resources to our VM running Jira (since we're not on EC2 we can put way more bang for our buck on VMs), we put a HTTP/2 proxy in front of it, we cache the hell out of it, even then it's still not as fast as it should be, but it's significantly faster than our experience with the cloud setup.
              • On top of this, a lot of 3rd party add-ons for Jira in general make Jira run like a dog at times, especially if someone is on a high latency/slow connection
              • Jira is already slow enough as-is to deal with Atlassian cramming us all together on shared infrastructure
            • JetBrains products have internal upgrade managers now, Jira still doesn't? Come on, you're intentionally breaking on-premises software.
            • Continue to lean into the "Agile" way of doing things, funny enough we don't use Agile boards almost at all, they get super cluttered really fast with what everyone is doing.

             

            On one hand you'd probably argue all the performance issues to be minor gripes, but we build high-performance software professionally, so seeing something like Jira run slow is annoying to us, especially being as we use it day-in and day-out, I don't want to consider another platform because Jira makes my team miserable to use it, and when you hire good engineers you basically try to do everything you can to make them happy

            You'll likely be fine to be honest, we're a picky bunch.

            William Roush added a comment - - edited Hey Nick Dring, just in general we had a few major gripes, we don't use DC though so we can't speak on the side of that. The new UI is a step down for a lot of us, being forced into it with no choice was annoying (yeah I know this can be the case with all UI changes but there is a reason a lot of people prefer things like Github to Bitbucket, don't follow Bitbucket's annoying UI) We always had worse performance, we give a nice bit of resources to our VM running Jira (since we're not on EC2 we can put way more bang for our buck on VMs), we put a HTTP/2 proxy in front of it, we cache the hell out of it, even then it's still not as fast as it should be, but it's significantly faster than our experience with the cloud setup. On top of this, a lot of 3rd party add-ons for Jira in general make Jira run like a dog at times, especially if someone is on a high latency/slow connection Jira is already slow enough as-is to deal with Atlassian cramming us all together on shared infrastructure JetBrains products have internal upgrade managers now, Jira still doesn't? Come on, you're intentionally breaking on-premises software. Continue to lean into the "Agile" way of doing things, funny enough we don't use Agile boards almost at all, they get super cluttered really fast with what everyone is doing.   On one hand you'd probably argue all the performance issues to be minor gripes, but we build high-performance software professionally, so seeing something like Jira run slow is annoying to us, especially being as we use it day-in and day-out, I don't want to consider another platform because Jira makes my team miserable to use it, and when you hire good engineers you basically try to do everything you can to make them happy You'll likely be fine to be honest, we're a picky bunch.

            On-premise starting @ $6k/yr? I get it's up to 500 users but geez that's rough when you need like.... 30.

            Also they're all-in on Agile which is one thing I appreciated Jira for, it was an add-on and we typically didn't use it.

            William Roush added a comment - On-premise starting @ $6k/yr? I get it's up to 500 users but geez that's rough when you need like.... 30. Also they're all-in on Agile which is one thing I appreciated Jira for, it was an add-on and we typically didn't use it.

              Unassigned Unassigned
              58b33c6e73c4 Henri Volk [amily]
              Votes:
              846 Vote for this issue
              Watchers:
              419 Start watching this issue

                Created:
                Updated: