However, every place I've been to that has done it, I've ended up removing it, because they have thousands of pointless or useless issues they have to kill off manually or chase up with <default text> in the description field.
Question why you want to do this, it's usually a waste of time just doing "default description", and often better to have dedicated fields instead, set mandatory. (For example, on stories, instead of injecting "as a ..., I want to..., so that..." in the description, have the who what and why as three separate mandatory fields)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs