• 7
    • 30
    • Hide
      Atlassian Update – 29 January 2019

      Hi everyone,

      Thank you 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.

      Meanwhile, you may consider using one of the apps for Jira Server available from the Atlassian Marketplace:

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

      For the Jira Server bugs and suggestions resolved in the last 6 months, including highly-voted features and improvements, please check this dashboard.

      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,
      Katarzyna Derenda
      Product manager, Jira Server

      Show
      Atlassian Update – 29 January 2019 Hi everyone, Thank you 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. Meanwhile, you may consider using one of the apps for Jira Server available from the Atlassian Marketplace: Issue Templates for Jira Repeating issues Simple Tasklist For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions: Further performance and stability improvements 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 Component archiving  JRASERVER-10507 Support for Jira on Microsoft SQL Server 2017  JRASERVER-66320 For the Jira Server bugs and suggestions resolved in the last 6 months, including highly-voted features and improvements, please check this dashboard . 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, Katarzyna Derenda Product manager, Jira Server
    • 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 Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Some tasks are allways the same, thej have same summary and description, components...like tasks for deploy. Now I solve this with tasks thet are never closed and when I need souch task I clone IT. This works fine, except that there are allways some open tasks.

      It wold be nice to have something like templates in confluence, where you can define template page..

            [JRASERVER-7731] Template issue

            Very disappointing to not see these 

            Maxim Fomin added a comment - Very disappointing to not see these 

            Templates for each issue type on project level is really needed.

            Jędrzej Dolata added a comment - Templates for each issue type on project level is really needed.

            Template for each issue type!! Mainly allowing users to pre-set text in the description field

            Sebastian Trucco added a comment - Template for each issue type!! Mainly allowing users to pre-set text in the description field

            I add to all of the above. Template feature is needed!

            Agnieszka Machielse added a comment - I add to all of the above. Template feature is needed!

            This would be very helpful.  My Jira user base is always asking for this type of feature to template the look and feel of ticket.

            Anne Gallant added a comment - This would be very helpful.  My Jira user base is always asking for this type of feature to template the look and feel of ticket.

            I would find this very helpful as well.   We have a great deal of standard/repeatable work that is requested from our clients.   Clone is not an option because Clone is brut force copy and there is plenty of data points on these issues that simply can't be copied.   The template is the ideal solution or develop a customizable cloning process that would allow you to set up cloning rules based on issue type.

            Jason Sheneman added a comment - I would find this very helpful as well.   We have a great deal of standard/repeatable work that is requested from our clients.   Clone is not an option because Clone is brut force copy and there is plenty of data points on these issues that simply can't be copied.   The template is the ideal solution or develop a customizable cloning process that would allow you to set up cloning rules based on issue type.

            you can create a custom field and for a custom field you can define a prefilled text. I did that for Story description so I give people hints that nothing is missed out. unfortunatelly with the new design this field is moving to the right column so I currently struggle with a very small field displayed which is the main description. It's so annoying that it's not possible to really define how screens look like. Atlassian probably tries to avoid mess by everybody doing his own screens but actually they create mess when people are forced to go for workarounds.

            Christoph Ranaweera added a comment - you can create a custom field and for a custom field you can define a prefilled text. I did that for Story description so I give people hints that nothing is missed out. unfortunatelly with the new design this field is moving to the right column so I currently struggle with a very small field displayed which is the main description. It's so annoying that it's not possible to really define how screens look like. Atlassian probably tries to avoid mess by everybody doing his own screens but actually they create mess when people are forced to go for workarounds.

            Max Nordlund added a comment - - edited

            This issue is about having a template option in vanilla Jira, not how to use some third-party app. Both mentioned above comes with a pretty hefty price tag when you start using Jira for more then just the dev team.

            Now, this issue is over 12 years old and in top ten for issues gathering feedback. My guess is that Atlassian doesn't intend to implement this feature because it may seem to be in conflict with Intenso's plugins.

            I believe there's room for both some basic functionally in vanilla Jira and leave the more advanced stuff for plugins, such as Intenso's one mentioned above. The most basic would be prefilled fields, without macros and interpolation, but it allows for some helpful text when someone is reporting an issue. This is how GitHub does it.

            Max Nordlund added a comment - - edited This issue is about having a template option in vanilla Jira, not how to use some third-party app. Both mentioned above comes with a pretty hefty price tag when you start using Jira for more then just the dev team. Now, this issue is over 12 years old and in top ten for issues gathering feedback. My guess is that Atlassian doesn't intend to implement this feature because it may seem to be in conflict with Intenso's plugins. I believe there's room for both some basic functionally in vanilla Jira and leave the more advanced stuff for plugins, such as Intenso's one mentioned above. The most basic would be prefilled fields, without macros and interpolation, but it allows for some helpful text when someone is reporting an issue. This is how GitHub does it.

            Using the power scripts app , you can create issue template automations and solve this use case. You can bulk copy projects, issues, attachments and even create a template of issues to launch and reuse quickly. (more info)

            Monte Montoya added a comment - Using the power scripts app  , you can create issue template automations and solve this use case. You can bulk copy projects, issues, attachments and even create a template of issues to launch and reuse quickly.  (more info)

            Hi,

            Please check the new release of Issue Templates for Jira app.

            https://marketplace.atlassian.com/plugins/com.intenso.jira.issue-templates/server/overview

            Best regards,

            Katarzyna

            Katarzyna Pawlak added a comment - Hi, Please check the new release of Issue Templates for Jira app. https://marketplace.atlassian.com/plugins/com.intenso.jira.issue-templates/server/overview Best regards, Katarzyna

              Unassigned Unassigned
              b724e41b253e Vid Jagodič
              Votes:
              440 Vote for this issue
              Watchers:
              208 Start watching this issue

                Created:
                Updated: