Hello Henrik,

Upgrading will not help for now, as there have been no changes in this area for a long time.

At the moment I unfortunately see no immediate solution to your problem, other than periodically reviewing unassigned issues.

However, you may be interested in checking out 0008582, I have a work-in-progress branch which could be useful for your purposes.

As what you require should be mostly covered by that branch, I am resolving this issue as duplicate. Please follow up in the other issue, or reopen this one if you feel it is not a duplicate.

Won´t reopen this issue yet.

Though 0008582 is not a "real" duplicate, the discussed solution "default category per project" would solve "my" issue.

... On the other hand: What´s the advantage to not allow an empty Category?

As you say, it's not really a dupe, I know that.

... On the other hand: What´s the advantage to not allow an empty Category?

There are cases, when one might want to force users to make a conscious choice, rather than using a default which may then reflect incorrect information (if they didn't bother to check).

Mantis does allow you to avoid that by setting $g_allow_no_category = ON; the default cat by project allows to go one step further.

In any case, any testing and feedback you may provide on https://github.com/dregad/mantisbt/tree/fix-8582-default-category would be appreciated (please report your comments in 0008582)