Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17430

Share settings with an existing project' is not applicable for new team-managed project

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

      Problem Definition

      While creating a new project with 'Share settings with an existing project', team-managed (formerly next-gen) projects are not an option.

      Suggested Solution

      Allow users copying the settings from an existing team-managed (formerly next-gen) project while creating a new one.

            [JSWCLOUD-17430] Share settings with an existing project' is not applicable for new team-managed project

            Pinned comments

            Dear Customers,

            After comparing this issue against another known report JRACLOUD-78729 – Ability to clone team-managed projects / add "Share settings with an existing project" option we realized that both are addressing the same scenario. Since we consider JRACLOUD-78729 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it.

            Best regards.

            Eduardo | Atlassian Support Team

            Eduardo Santos added a comment - Dear Customers, After comparing this issue against another known report JRACLOUD-78729 – Ability to clone team-managed projects / add "Share settings with an existing project" option we realized that both are addressing the same scenario. Since we consider JRACLOUD-78729 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it. Best regards. Eduardo | Atlassian Support Team

            All comments

            Dear Customers,

            After comparing this issue against another known report JRACLOUD-78729 – Ability to clone team-managed projects / add "Share settings with an existing project" option we realized that both are addressing the same scenario. Since we consider JRACLOUD-78729 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it.

            Best regards.

            Eduardo | Atlassian Support Team

            Eduardo Santos added a comment - Dear Customers, After comparing this issue against another known report JRACLOUD-78729 – Ability to clone team-managed projects / add "Share settings with an existing project" option we realized that both are addressing the same scenario. Since we consider JRACLOUD-78729 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it. Best regards. Eduardo | Atlassian Support Team

            Hey 0a78c8263cec thanks for your response. I take your point about sharing settings between projects not being the same as cloning a project. I'm also following up internally on both requests.

            Anusha Rutnam added a comment - Hey 0a78c8263cec thanks for your response. I take your point about sharing settings between projects not being the same as cloning a project. I'm also following up internally on both requests.

            Added vote to the other ticket as well and started following there as well.

            Peter Nicolai Alexis Kyaw added a comment - Added vote to the other ticket as well and started following there as well.

            Hi, the other ticket is about cloning a project even though the comments also refer to sharing the settings. Cloning a project and sharing settings is not exactly the same thing to me. Maybe the title of the other ticket should be modified. I also noted that there is an official comment that the feature will be added, just not in the next 12 months, which is from 2020. Which means nobody cares about this critical topic and Atlassian is leaving the clients that have big projects behind. Big projects means big companies and there employees are used to accepting a lot of bullshit without complaining much, which is why you see so few votes on this - people just suffer from the shitty way configuration is handled and do the "sharing" by manually copying. I actually stopped using Jira myself - my client (yes, a very big company) is handling all the configuration trouble now.

            Peter Nicolai Alexis Kyaw added a comment - Hi, the other ticket is about cloning a project even though the comments also refer to sharing the settings. Cloning a project and sharing settings is not exactly the same thing to me. Maybe the title of the other ticket should be modified. I also noted that there is an official comment that the feature will be added, just not in the next 12 months, which is from 2020. Which means nobody cares about this critical topic and Atlassian is leaving the clients that have big projects behind. Big projects means big companies and there employees are used to accepting a lot of bullshit without complaining much, which is why you see so few votes on this - people just suffer from the shitty way configuration is handled and do the "sharing" by manually copying. I actually stopped using Jira myself - my client (yes, a very big company) is handling all the configuration trouble now.

            I believe this issue is a duplicate of JRACLOUD-78729 – Ability to clone team-managed projects which has more votes.

            I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            Anusha Rutnam added a comment - I believe this issue is a duplicate of JRACLOUD-78729 – Ability to clone team-managed projects which has more votes. I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            My organisation is working on a small typical projects and we need to create a new project in Jira every 2 weeks. I believe this is not a rare case within consulting sector. Please introduce this feature, it would make our life so much easier. Btw, we switched to Jira because we thought that setup of projects will take less time than in our legacy system. Apparently it's not

            Ivan Luzhnyi added a comment - My organisation is working on a small typical projects and we need to create a new project in Jira every 2 weeks. I believe this is not a rare case within consulting sector. Please introduce this feature, it would make our life so much easier. Btw, we switched to Jira because we thought that setup of projects will take less time than in our legacy system. Apparently it's not

            how can this not be a thing yet?

            James Poole added a comment - how can this not be a thing yet?

            This would be very helpful please develop

            Alberto Misrachi added a comment - This would be very helpful please develop

            Dolev Sall added a comment -

            Needed. Very needed.

            Dolev Sall added a comment - Needed. Very needed.

            Also got into a situation, where one team that works in one Next-Gen project needs to be split in two teams and each team needs to have it's own projects (one team stays in the existing and the other one is asking for creating exactly the same project as the previous one). 

            Google search has suggested this topic, that was created back in the 2018 and still isn't solved...  Right...

            Egils Sverns added a comment - Also got into a situation, where one team that works in one Next-Gen project needs to be split in two teams and each team needs to have it's own projects (one team stays in the existing and the other one is asking for creating exactly the same project as the previous one).  Google search has suggested this topic, that was created back in the 2018 and still isn't solved...  Right...

              Unassigned Unassigned
              vrai@atlassian.com VR
              Votes:
              169 Vote for this issue
              Watchers:
              114 Start watching this issue

                Created:
                Updated:
                Resolved: