Set permanent text in discriptions field for specific projects

Question

Hi Atlassian.

A team in in our jira wants to modify how to wright a bug ticket in our environment.

They want to place a text in the description field, which is a system field, and that is liked to only issue "bug" and for only the specific 7 project this relates to.

What is best way to do this. We do not have scriptrunner, but i was thinking maybe i can automate this or something for when a ticket is in creation state? the text should be permanent, and not able to remove by user.

Also they want to add a link to our confluence page, where there is more information regarding the subject.

Please help me with best practice om this.

Stephanie Parhorn Rohdin_1ahqot · Answer

?

Stephanie Parhorn Rohdin_1ahqot · Answer

Hi again.

The text is for bug tickets, with is more of a information text, that makes the user that creates tickets (bug tickets) aware of what kind of information needs to be in the ticket to be able to help them in the best way possible.

If there was just a new field then the message could be missed, as it has been with the likned documentation. Therefor they want to implement the text in the "description-field".

Hope that made it more clear.

Do you have any different suggestions, and/or if this is possible?

Best Regards ,

Stephanie

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community! This sounds like you might be talking about "default" text in the description field. Whilst this is not an uncommon thing to ask for, it has two huge problems. Let's say you default the text in the description to "as a , I want , because ". The idea is that people will then fill in the three sections. In real life, they won't. Not only will they destroy the preset text you want to keep, you're going to end up with tens of thousands of issues with utterly useless descriptions containing nothing but the default. I would strongly recommend a look at the text your people want to use. Would the responses from the users be useful as separate fields? Where you can give them informative names, and helpful field "descriptions" (which would both be permanent and clear).