Victor Boctor

The associated issue was closed with a commit from @dregad - closing PR.

@CasN Thanks for your patience on this. I had another look and here are my thoughts: If we are to go with the approach in this PR, then here are...

Thanks @starlocke for working on this. It is a change that touches a lot of areas. I had a look and have the following comments: 1. It feels like we...

You may want to consider working on the core concept and few pages (3-4) and once we settle on the approach and have it working there, then we can expand...

Thanks @AidenY69 - these are a lot of domains, what is the source you used to figure out all of these domains?

We should probably have a different branch for 1.2.x vs. 1.3.x vs 2.0.x. @dregad what do you think?

@luzpaz I was thinking about the same feature, but the solution I had in mind was more inline with how [Github solves this](https://help.github.com/articles/creating-an-issue-template-for-your-repository/). Basically, to do be able to configure...

@atrol I think this is better handled in core, since it not a snippet and it would be consistent with ability for core to default other native fields.

Turns out that steps to reproduce and additional info already supported defaulting. I have added support for defaulting description via the following PR: https://github.com/mantisbt/mantisbt/pull/1320

@dregad done.