nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I pre-populate text to a description field on JIRA Cloud version 7.x?

rosebud0911

I have tried all the Javascript solutions I've found already and they only seem to add the code as txt to the grey'd out area beneath the text box (like a label).

Accepted answers

Ignacio Pulgar

You can do it by creating custom fields.

In order to do so:

Enter JIRA, press the 'g' key twice and type 'custom fields'.
1. Click on the button 'Add Custom Field', on the top right corner.
2. Select a text field (multi-line or single line). Click 'Next'.
3. Give it a name and, optionally, a description.
4. Click on Create.
5. Select the project(s) checkboxes in which you want to include your custom field.
6. Click on Update button.
On the Custom Fields page, find the name of your custom field and click on the icon in the right > 'Configure'.
configure.jpg
1. Click on the link 'Edit default value'.
2. Type the description you wish to be populated as the default for that given field.
3. Click on the 'Set Default' button.
Repeat this process again for each text field in which you want to have a different default value.

After that, associate your custom fields to the screens in which you wish to have them.

configure.jpg

All comments

Nic Brough -Adaptavist-

Essentially, you can't - javascript hacks in JIRA are gradually being disabled, and the approach here is to get a good answer to "why are you trying to put useless data into fields?". What are you trying to achieve by pre-populating the description? Why haven't you split that up into custom fields which do take defaults? What use is a description people will just accept instead of putting good data into? Why don't you just remove the description field if you're not going to ask people to think about its content?

rosebud0911

Because it isn't pre-populating that actual data rather the information for the standard answers that need to be given on each issue that is filed. It is basically a template that MUST be filled out on every ticket. A gentle subtle ... in your face reminder of what is required to be in that field.

Ignacio Pulgar

You can do it by creating custom fields.

In order to do so:

Enter JIRA, press the 'g' key twice and type 'custom fields'.
1. Click on the button 'Add Custom Field', on the top right corner.
2. Select a text field (multi-line or single line). Click 'Next'.
3. Give it a name and, optionally, a description.
4. Click on Create.
5. Select the project(s) checkboxes in which you want to include your custom field.
6. Click on Update button.
On the Custom Fields page, find the name of your custom field and click on the icon in the right > 'Configure'.
configure.jpg
1. Click on the link 'Edit default value'.
2. Type the description you wish to be populated as the default for that given field.
3. Click on the 'Set Default' button.
Repeat this process again for each text field in which you want to have a different default value.

After that, associate your custom fields to the screens in which you wish to have them.

configure.jpg

Nic Brough -Adaptavist-

Ah, all the wrong answers as usual. If you pre-populate a text field, people will ignore it. If you need it to fulful a certain format, people will overwrite that too. Convert it to a set of fields, leave them blank (unless you genuinely do have solid defaults for them) and set them mandatory to force people to enter them and think about it. In places where people set text defaults, you find that between 60% and 99% of issues will have the defaulted text and nothing else (the more complex you make it, the higher the percentage as a general rule).

Ryan Thomas

We use Bug issue types.
I want my testers to enter a standard format for bugs in the description of the bug. I don't want to add another custom field for something the Description of the bug should handle.

You cannot do this is acceptable.

You shouldn't because my arbitrary experience tells you not to isn't always acceptable.

STEPS TO REPRODUCE:
1.
2.

EXPECTED RESULT:

ACTUAL RESULT:

This should be available in Cloud version.

pace_wstaves

I want to do the same thing as other people have mentioned on here. Pre-populate the description with a template structure

Steps to reproduce

Observed behavior

Desired behavior

Hopefully someone will see that there are several people here that desire this functionality, and help us achieve it, rather than beat us over the head with their opinions about custom fields.

Nic Brough -Adaptavist-

As before - JIRA doesn't do this natively, so you have to hack it.

I'm afraid for Cloud, there's no real way to do it, unless you start doing things with browser add-ons.

Custom fields are your only option, irrespective of any opinions.

Ryan Thomas

Ignore:

Nic Brough -Adaptavist-

This does not work. It actually makes the problem even worse.

It does add a pre-filled description on creation of the issue. After you create it. Every issue done this way has the default text in the description, and users have no reason to go back and edit it.

unknown

I will need to move to the server version for this functionality. Well if this is the case and users are given helpful nudges or hints on what and where to add necessary information I see no downside.

Fermulator

One user mentioned it already, but here's the link:

https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

Using "Behaviours" from the ScriptRunner plugin should exactly solve this request.

Nic Brough -Adaptavist-

Again, bad idea, and it's not valid for Cloud.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

test