• 108
    • 133
    • Hide
      Atlassian Update – 3 September 2018

      Hi everyone,

      Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      When creating new project you can select either a project type depending on which Jira applications you have installed or Create with shared configuration to select an existing project and to use that project's schemes. Using this capability may be applicable in some use cases described in comments. When you're sharing schemes, any change to the scheme will affect all the projects using that scheme. You can read more about creating new project in Jira Server documentation.

      If creating projects with shared configuration is not sufficient, you may consider commercial third party apps available from the Atlassian marketplace, which may be useful in your context.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including several of highly-voted suggestions from you:

      In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including:

      • Filters and dashboards collaborative editing
      • Selectable delimiters in CSV export 
      • Microsoft SQL Server 2016 support 
      • iPv6 support
      • Faster Kanban boards
      • Refreshed projects and custom fields management pages in the admin's section 

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,

      Jira Server Product Management

      Show
      Atlassian Update – 3 September 2018 Hi everyone, Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. When creating new project you can select either a project type depending on which Jira applications you have installed or Create with shared configuration to select an existing project and to use that project's schemes. Using this capability may be applicable in some use cases described in comments. When you're sharing schemes, any change to the scheme will affect all the projects using that scheme. You can read more about creating new project in Jira Server documentation . If creating projects with shared configuration is not sufficient, you may consider commercial third party apps available from the Atlassian marketplace, which may be useful in your context. Configuration Manager for Jira Delegated Project Creator for Jira Gaia for Jira - Project Template Manager Project Configurator for Jira For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including several of highly-voted suggestions from you: Further performance and stability improvements Email notifications template editor available from the UI  JRASERVER-7266 Jira email notifications batching  JRASERVER-1369 Mobile app for Jira Server  JRASERVER-46149 Improved filter and dashboard management by Jira administrators  JRASERVER-15900  and  JRASERVER-41269   Adding the "updated-by" JQL search query  JRASERVER-1973 Support for 4 byte characters in MySQL connection  JRASERVER-36135 In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including: Filters and dashboards collaborative editing Selectable delimiters in CSV export  Microsoft SQL Server 2016 support  iPv6 support Faster Kanban boards Refreshed projects and custom fields management pages in the admin's section  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more on how you suggestions are reviewed, see our  updated workflow for server feature suggestions . 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.

      Original request description:

      This will allow admins to have a project template(that includes issues, attachments, and comments) that can be copied each time a new project is selected. This will save the admins time from associating new projects with schemes after creation.

      One way to implement this would be to create 'project schemes’.

            [JRASERVER-7020] Allow support for project schemes or templates

            Sherri Sharpe added a comment - - edited

            Being able to create a new Jira project from a template one is a key requirement going forward.  We badly need this! Even being able to copy the issue tickets from a basic template Jira board but with no dependency links would be helpful as a first step. 

            Sherri Sharpe added a comment - - edited Being able to create a new Jira project from a template one is a key requirement going forward.  We badly need this! Even being able to copy the issue tickets from a basic template Jira board but with no dependency links would be helpful as a first step. 

            This would be so helpful. I take my time to customize by boards and projects and hate having to do it all over again for the next project. Fully support the development of this feature. 

            Solana Rosa added a comment - This would be so helpful. I take my time to customize by boards and projects and hate having to do it all over again for the next project. Fully support the development of this feature. 

            Marco Cetina added a comment - - edited

            Any updates on this?

            Marco Cetina added a comment - - edited Any updates on this?

            Is there any update on this?

            Being able to re-use a project template including the full ticket structure is a pretty basic need that many Jira users will benefit from.

            Lucy Harding added a comment - Is there any update on this? Being able to re-use a project template including the full ticket structure is a pretty basic need that many Jira users will benefit from.

            Create a Project through template is a great feature in Jira,

            we have noticed that when we create a new project through template it is not creating project specific new context to add a project specific dropdowns, and also we have created some behaviors as a part of automations and we expect our new project get mapped to it automatically when we create project through template,

            Please let us know whether we have any option to achieve above features?

            We are using Jira Data Center.

            Thanks,

            Santhosh

            santosh.bhatt_ext added a comment - Create a Project through template is a great feature in Jira, we have noticed that when we create a new project through template it is not creating project specific new context to add a project specific dropdowns, and also we have created some behaviors as a part of automations and we expect our new project get mapped to it automatically when we create project through template, Please let us know whether we have any option to achieve above features? We are using Jira Data Center. Thanks, Santhosh

            Future Consideration? It's been 15+ years. Highly unlikely!!!

            Dale Keller added a comment - Future Consideration ? It's been 15+ years. Highly unlikely!!!

            kderenda@atlassian.com,

            Your last roadmap update from February used to include the item "Optimising the use of custom fields" but for some reason your team specifically excluded JRASERVER-6851:
            "Allow more than one custom field context to be associated with the same project but different issue types." This would seem to be a pivotal feature in "optimising the use of custom fields" but the status of this highly-voted issue remained "Not being considered."

            Now your roadmap now makes no mention of "Optimising the use of custom fields." Have you given up on this goal? Or do you feel you've accomplished this goal without addressing the key problem of multiple custom field contexts?

            Andrew Culver added a comment - kderenda@atlassian.com , Your last roadmap update from February used to include the item " Optimising the use of custom fields " but for some reason your team specifically excluded JRASERVER-6851 : "Allow more than one custom field context to be associated with the same project but different issue types." This would seem to be a pivotal feature in "optimising the use of custom fields" but the status of this highly-voted issue remained "Not being considered." Now your roadmap now makes no mention of "Optimising the use of custom fields." Have you given up on this goal? Or do you feel you've accomplished this goal without addressing the key problem of multiple custom field contexts?

            I would love to have the functionality to copy projects on a hosted environment, for our business and continuity this would make life a lot easier, I'm having to create the exact same project on our instance of Jira for another client. It would be great to look into this as I do believe there should be a huge demand for this functionality to exist.

            Nicole Glen added a comment - I would love to have the functionality to copy projects on a hosted environment, for our business and continuity this would make life a lot easier, I'm having to create the exact same project on our instance of Jira for another client. It would be great to look into this as I do believe there should be a huge demand for this functionality to exist.

            This should be simple to do and a basic feature for any tool like this. We do a lot of projects that are similar and need to copy a complete project with issues and everything to limit the workload and limit errors in issue creation and project setup.

            Ricky Lindgaard Nielsen added a comment - This should be simple to do and a basic feature for any tool like this. We do a lot of projects that are similar and need to copy a complete project with issues and everything to limit the workload and limit errors in issue creation and project setup.

            If it's not revenue protection, what then keeps Atlassian from implementing massively requested and honestly naturally expected features?

            Any other professional product that does not rely on Plugins would include such a feature.

            Ernesto Portillo added a comment - If it's not revenue protection, what then keeps Atlassian from implementing massively requested and honestly naturally expected features? Any other professional product that does not rely on Plugins would include such a feature.

              Unassigned Unassigned
              anton@atlassian.com AntonA
              Votes:
              965 Vote for this issue
              Watchers:
              425 Start watching this issue

                Created:
                Updated: