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

Default values of system fields

XMLWordPrintable

    • 1,112
    • 72
    • Hide
      Atlassian Update – 19 March 2021

      Hi everyone,

      thank you for all your votes and comments on this suggestion.

      Since Jira Data Center version 8.16 we're introducing a possibility to configure a default value for the Description field. From now on, admins can add and apply contexts with a default value to multiple issue types and projects (working exactly as currently for custom fields). We added a separate page in the admin panel, that lists all system fields - with Description field as the only editable. You can learn more about it how it works here: 

      For the future we considering extending the functionality by:

      • adding other system fields to be configurable e.g. summary or fix version that you have mentioned in the comments under this issue.
      • giving the rights to set up default values to Project Level Admins.
      • extending this functionality for JSM Customer Portal.

      To make the best decision, we’d like to hear your feedback. For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-72239. We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there.

      To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA.

      Other than that, we would like to clarify is that this project is for Jira Data Center only. For Jira Cloud admins can set a default value on the Description field in Next-gen projects, for Classic projects please vote and follow the issue at JRACLOUD-4812.

      Thank you,
      Grażyna Kaszkur
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 19 March 2021 Hi everyone, thank you for all your votes and comments on this suggestion. Since Jira Data Center version 8.16 we're introducing a possibility to configure a default value for the Description field. From now on, admins can add and apply contexts with a default value to multiple issue types and projects (working exactly as currently for custom fields). We added a separate page in the admin panel, that lists all system fields - with Description field as the only editable. You can learn more about it how it works here:  For the future we considering extending the functionality by: adding other system fields to be configurable e.g. summary or fix version that you have mentioned in the comments under this issue. giving the rights to set up default values to Project Level Admins. extending this functionality for JSM Customer Portal. To make the best decision, we’d like to hear your feedback. For this purpose, we've created a new suggestion focused entirely on collecting feedback and ideas for further improvements: https://jira.atlassian.com/browse/JRASERVER-72239 . We’ll use it to keep engaging with you on this topic, so please drop all your thoughts there. To avoid having multiple suggestions about the same topic, we’re closing this one as fixed. It doesn’t mean that no further work will be done in this area. This will help us streamline your feedback and identify some missing parts that we still need to incorporate into JIRA. Other than that, we would like to clarify is that this project is for Jira Data Center only. For Jira Cloud admins can set a default value on the Description field in Next-gen projects, for Classic projects please vote and follow the issue at  JRACLOUD-4812 . Thank you, Grażyna Kaszkur Product Manager, Jira Server and Data Center
    • 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.

      I would like to provide default values not only for custom, but also for system fields.

      An example:
      Depending on the issue type, I would like to provide different default values for the field "Description" which help users to fill in e.g. the details of a bug issue.

        1. image-2017-07-11-17-20-50-674.png
          image-2017-07-11-17-20-50-674.png
          23 kB
        2. jira.JPG
          jira.JPG
          38 kB
        3. JIRA-4812-Example_Issue_Create_Form_With_Placeholder-Default_Text.png
          JIRA-4812-Example_Issue_Create_Form_With_Placeholder-Default_Text.png
          70 kB

            [JRASERVER-4812] Default values of system fields

            Igor Solovei added a comment -

            What about this task?

            Igor Solovei added a comment - What about this task?

            Oliver Wasiak added a comment -

            Just like @Deepali mentioned, it would be great to have the possibility to set multiple contexts for system fields per project. This way every issue type could have a dedicated description within a project. Many thanks for your support.

            Oliver Wasiak added a comment - Just like @Deepali mentioned, it would be great to have the possibility to set multiple contexts for system fields per project. This way every issue type could have a dedicated description within a project. Many thanks for your support.

            Deepali Deshpande added a comment -

            It would be great if we can get this functionality available to be configured within Jira Data Center. Maintaining  & customizing Description Field Templates for various projects and issue types within whole organization is very repetitive task. If we can get something Jira Admins can configure at Project and Issue Type level would be a game changer. Please provide some inputs. Thank you!

            Deepali Deshpande added a comment - It would be great if we can get this functionality available to be configured within Jira Data Center. Maintaining  & customizing Description Field Templates for various projects and issue types within whole organization is very repetitive task. If we can get something Jira Admins can configure at Project and Issue Type level would be a game changer. Please provide some inputs. Thank you!

            vadim.arkadov added a comment -

            @Grazyna Kaszkur

            Any news about the fate of this task?

            vadim.arkadov added a comment - @Grazyna Kaszkur Any news about the fate of this task?

            Evgeniy Terentyev added a comment -

            Unfortunately, there is no clear instruction on how and where I can set that "default" text for the Description field (per Issue Type for a Project). Could someone please help?

            Evgeniy Terentyev added a comment - Unfortunately, there is no clear instruction on how and where I can set that "default" text for the Description field (per Issue Type for a Project). Could someone please help?

            Bernhard Reiter added a comment -

            Why is this feature restricted to Data Center? Server customers are forced to switch 2023...so no need for giving incentives with holding back features. 

            Bernhard Reiter added a comment - Why is this feature restricted to Data Center? Server customers are forced to switch 2023...so no need for giving incentives with holding back features. 

            Lloyd Bullard added a comment -

            Thanks Greg - the organization I work for is quite small, and for a variety of mostly good reasons we are not adding any extra plugins to JIRA. There appears to be no clear and easy way to get what is in the screenshot shown in the issue description on this ticket.

            I am just looking for a basic set of easy to use instructions like Github has for the same feature that do not include me having to do things like "download and modify this .json file" - 

            https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

            Lloyd Bullard added a comment - Thanks Greg - the organization I work for is quite small, and for a variety of mostly good reasons we are not adding any extra plugins to JIRA. There appears to be no clear and easy way to get what is in the screenshot shown in the issue description on this ticket. I am just looking for a basic set of easy to use instructions like Github has for the same feature that do not include me having to do things like "download and modify this .json file" -  https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

            Greg Hoggarth added a comment -

            IMO the best way is the Behaviours component of Jira script runner plugin, however this is a paid plugin so you may not have it.

            Greg Hoggarth added a comment - IMO the best way is the Behaviours component of Jira script runner plugin, however this is a paid plugin so you may not have it.

            Lloyd Bullard added a comment -

            I have been reading up on ways to get default templates into one of my projects for ages - this seems to be the answer but the information is not detailed enough for me to understand exactly how and where to go to get started. there is too much assumed knowledge in the parent issue and all of the comments, and many of the comments refer to Jira as it was a decade ago as this issue is ancient. is there a nice, simple set of steps documented somewhere so that I can get the results seen in the attached screenshots? 

            Lloyd Bullard added a comment - I have been reading up on ways to get default templates into one of my projects for ages - this seems to be the answer but the information is not detailed enough for me to understand exactly how and where to go to get started. there is too much assumed knowledge in the parent issue and all of the comments, and many of the comments refer to Jira as it was a decade ago as this issue is ancient. is there a nice, simple set of steps documented somewhere so that I can get the results seen in the attached screenshots? 

            Vladimir added a comment -

            @chyren

            I think you chould create new request.

            I know from other tools this functionality. It was very good because every user could have its own defualts values.

            When you create new issue every user there has button "Default Values", there can be select every field and user can add any value. Then there can be checked if these values should be added automaticaly every time the new form is opened. If not then user mus click one button and the values are filled in. 

            This is very convenient and usefull.

            Vladimir added a comment - @chyren I think you chould create new request. I know from other tools this functionality. It was very good because every user could have its own defualts values. When you create new issue every user there has button "Default Values", there can be select every field and user can add any value. Then there can be checked if these values should be added automaticaly every time the new form is opened. If not then user mus click one button and the values are filled in.  This is very convenient and usefull.

              abienias@atlassian.com Adrian Bienias (Inactive)
              37c65ac6191b Frank Schimmel
              Votes:
              2046 Vote for this issue
              Watchers:
              816 Start watching this issue

                Created:
                Updated:
                Resolved: