What about this task?

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.

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!

@Grazyna Kaszkur

Any news about the fate of this task?

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?

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. 

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

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.

@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.

Hi,

Is it possible to extend it to create personal templates? Such as some guy works on a part of the project as day to day, and file Jira frequently, and fill some custom fields most time with the same values. If it's done with templating, it could save a lot of time.

A few comments after reading the 8.16 release notes.

I would love to see the configuration extended to project admins to reduce Admin burden.

Also makes perfect sense to extend to JSM, but keep in mind JSM templates will probably change based on Request Types, not Issue Types. I implemented a Script Runner solution but would love to see something more robust built-in.

Hi, attila.kuti,

Take a look at this in the release notes: https://confluence.atlassian.com/jirasoftware/jira-software-8-7-x-upgrade-notes-987138245.html#JiraSoftware8.7.xupgradenotes-DisablingHTMLincustomfieldsdescription. Is this change related to the problem you're experiencing?  You'll find how to fix in under that link.

If you have any feedback about this change, please head to its ticket: JRASERVER-70859.

Hi, we are testing Jira 8.14 and realized that the default value javascript in e.g. Summary field description stopped working (Jira Server). Why is that?

thanks

Hi,
When is it expected to be available for Jira data center?

Lester, you sure it's only one sided? Or is your point of view one sided?

Think of API tokens, which are still to be backported to LTS, There is lot of other items...

Ha! Jira cloud lags WAAAAAAY behind (if at all).  There is an endless list of features that have never made it to Jira cloud. So cool to read some issue you are aware of was fixed... a year ago... only to find that fix never made it to Jira cloud.  Consider the request to not show every Sprint from every project across all time when selecting a sprint. That fix never came to Jira cloud.    

Hej, when will this be available in Jira Cloud?

This is already available or going to be available for Jira Service Desk? If so, when? 

What is the expected date to have this feature deployed? 

Great news. But please don‘t forget the summary  

Use Case:

We update the summary with automation based on other fields. E.g. a „Contact“ issue has as summary „First name + Last name + Company name“. But the summary could only be set by automation after the issue is created. Due to the fact, that summary is mandatory on issue creation, users have to fill in the information twice.

With having the possibility to set a default value for summary too, we could withdraw the summary field from issue creation screen. 

Will you be adding this functionality for Jira Software on Cloud?

Preferably I would like to be able pre populate the description of stories with a specific text and the issue type bug with a different text.

Right on time! as I thought that it will be another limitation...

I hope default vaue will mean value which will be pre popped up on the ticket creation screen and not after ticket is created.

Looking forward to have this implemented on Jira cloud, I hope Jira Data center is the one.

I also add the note. The definition of this case is not to define default value by project but by issue type.

But I hope that you will not create new way how to fill the default value. You should follow your own system where when I want the default value I create field configuration. 
So you do not need to thing out anything new. You just add the defalut value for existing field configuration for all fields. Thats all. You can start with description and if you will follow it then it will be not only by project but also by issue type as needed.

My question is. This is for Jira server but you wrote for Jira Data center. Hope it will be available also for server?

I have also my own suggestion how to do this universaly not just "half way". Becuase I can pretend that the default value by issue type will not be anough for some cases. It would be best if there will be some sort of filter or script that will be applied for that particular field configuration field and the default value will be filled in only if the issue is in the filter or the condition is true. Pretend this:

1. you want default value for all stories like "ABC"
2. you want default value for stories created from epics "DEF"

You can achieve it very simply if you add condition to default values like:
I cannot add attachments:

• just add the option "Defaults" for the field configuration field
• after clicking to the option open new window where I can fill more defaults (three colums), first is name, second is condition and last is the value.
• and lastly the value should be a standard Jira text or script so you can achive anythink what you want.

Totally agree, and great pickup by Kate.  Default-by-issue-type is totally mandatory - a "default description for all issues in a project" would be useless.

This is great news, thank you Atlassian.
One thing that must be important for most teams, is ability to define Description templates on the issue type level (and not merely on the project level). E.g. a similar default text for Stories and Bugs would hardly support any use case. I hope that's a fair expectation and thanks for being open to feedback!

Hello everyone,

Thank you for your votes and comments on this issue. We have analysed all the use cases mentioned in the comments and we would like to inform you that our team has started working on this issue for Jira Data Center.

We are focusing on the “Description” system field and we will add a possibility in the admin panel to set its default value per project. We are doing this to address the need of creating issues with the template text already filled in, without the need to copy it manually each time.

While we are working on the solution, we are open to hearing additional feedback. Please feel free to leave us a comment in the thread below.

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

Maybe we don't need that feature.
Because it's cause a huge problem for big instances

Created in 2004... That's like a generation

@Mick van Breukelen - please check first line of the Description field that links to the corresponding JRACLOUD issue.

If I vote yes here, will I also vote for this feature in Jira Cloud?

I don't know if I should laugh or cry...

Can someone just give the ticket "the final shot" and just close it? I don't think theres anybody left in the world of Atlassian who believes this will get implemented.

@alex_kazarin no

In the plugin we use (Field Tempaltes for Jira) you can set up templates (paste in 1 click) in some field. The good thing is that you can set up templtes depending on issue type. So, like if you have "Bug" you set up "steps to reproduce" in the template, but for "Task" you would not see it. Quite comfy. =)

@DimitarMilanow have you found any solution about checking by issue type?

Does anybody have suggestions (request above, in previous comment)?

https://confluence.atlassian.com/display/JIRA044/Setting+a+Default+Value+in+the+Description+Field?_ga=2.150556086.142735240.1511440734-267596140.1479888067
How can I check what is the issue type in this example ? something like 
#if($description == '' && $issue.type == "Bug")
#set ($description = "Steps to Reproduce")
#end
Thanks in advance!

Check out Workflow Essentials for Jira. It let's you define default values for system and custom fields on the create issue screen.

Hi everyone! Does anybody know - is it possible to specify Project, when configuring Default Value in the Description Field (https://confluence.atlassian.com/display/JIRA044/Setting+a+Default+Value+in+the+Description+Field?_ga=2.150556086.142735240.1511440734-267596140.1479888067) ? How could I do this?

Thank you in advance!

We should create a Twitter acct for it.  #fixit #wewontgiveup #15dogyears #isanyonehome

This is like the little issue that could.  It has somehow managed to stay alive since 2004 (like Jira 1.0 I suppose).  And 16 months ago it was posted that it would be reviewed in 12 months and maybe be considered for the long term roadmap.  And this issue still keeps collecting votes and won't be deterred. 

Please push this up the backlog / back into consideration. It is approaching its 15 year anniversary!

Or is the notion to just plugin our way around this?

I think Default Values for 'Create Issue' screen add-on may be useful.

ilay Correct, my bad- will move along to the next ticket. Thanks for pointing it out!

tomas.jonsson This particular ticket is for the Jira Server feature request. You may want to follow the Jira Cloud request here: https://jira.atlassian.com/browse/JRACLOUD-4812

@Miron Smart - We use Jira Cloud, as far as I understand from the plugin overview- it is made for use with Jira Server. 

We also wanted this feature for so long! The solution in the comment above (about "Field Templates for Jira" plugin) saves us tons of time =) Thanks a lot.
Atlassian, isn't it enough to start implementing the feature after it's being asked for almost 15 years in a row by so many people?

Created:  06/Oct/2004 3:50 PM

 
This is 14 years old now, there should have been 14 reviews according to the 12 months policy of reviewing requests such as this done by now.
 
Can we expect this to be developed at any point or is it simply not anything you wish to offer to Jira Cloud users? It would greatly improve the reporting of issues coming from other teams that not necessarily has the same background in project management or requirement reporting. 

Please implement this feature as then we can use an issue as template and will save lot of time. This is critical for implementing Jira.

Please implement this feature or release in Jira sdk for customized development, thanks. 

PLEASE implement this. I've recently switched to the Cloud instance of Jira, which is supposed to have all the newest features, but I feel like I've taken a huge step backwards, with my whole team having to type out a whole swathes of text for every entered issue. It's a bit farcical :/ 

And....this ticket is SO old. Come on guys. 

andrea.rosskamp2, I agree Jira is missing lots of "obviously needed" functionalities that users wanted for years like description default values or many other. Yet Atlassian maybe has it's own reasons like... architecture?. Anyway this "Field templates for jira" helped to cure the pain of copy-paste routine. 

Anyway we all solve our problems as we can =) 

a_sobolevskiy added a comment - Yesterday
Folks! Perhaps this helps. A plugin that can do field population - https://marketplace.atlassian.com/apps/1219597/field-templates-for-jira?hosting=server&tab=overview

Hope you find this info useful. 

Thanks for this information. But in this case I couldn't argument for an AddOn. Some functionality is really expected in the standard. This is not an edge case and it is limited functionality in the standard (as you can add default values for custom fields in the standard).

Folks! Perhaps this helps. A plugin that can do field population - https://marketplace.atlassian.com/apps/1219597/field-templates-for-jira?hosting=server&tab=overview

Hope you find this info useful.

Dear Atlassians,

I agree with this feature. It will be very useful specially for a young organization where the staffs do not know how to write a proper ticket

Dear Atlassian,

could you at leats please implement some kind of templating for the description? This feature is needed for so long!

User Story

As a Product Owner I want to add a template for the the issue types bug, user story, and task, so that I do not have to type in the same description structure everytime I create an issue and have a guide for new team members on how to document these issues properly.

Any updates?

It's been 14 years. Your guess is as good as our's.

Will Atlassian add this feature or no?