Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I would like to have the "description" field appear with some text to act as a template. I only want this to affect the "bug" issue type.
I have been tinkering for a bit, but I can only seem to edit custom fields, not "core" fields.
Example:
Upon selecting the bug issue type, the description field shows the following text:
*Description*
*Steps to reproduce* etc.....
Hi @Otto,
You can prepopulate the description field using an add-on like Power Scripts.
We've actually put together a quick 8 min video tutorial that walks through all the steps you need to take to set this up. And we've also included the sample code we used, so you can just copy and paste it to test for yourself.
Hope this helps!
Johnson
You need ScriptRunner's Behaviours for prepopulating the Desciption field that way:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's correct. Description is for a human to describe something, and should not be defaulted. When you do default it, you end up with metric shed-loads of identical and pointless descriptions completely wasting everyone's time, and when the users do enter data, it's not very categorisable when you search. A far better option than this is to create set of appropriate, separated, and clear text fields - steps to reproduce, observed behaviour, desired behaviour, etc. You can default these, but because you're now structuring your data correctly, you'll find you don't need to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I fundamentally disagree. The example used in the tutorial of what Ignacio suggested, you can see it doesn't have to be the case. All QA work I have ever done in JIRA had prepopulated fields and they were all filled in. Always, and by all team members.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic - I certainly see the problem, but can't you also set a validator to make sure that the user changed from the default?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register Now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.