At this point, I think we do not need to make this pattern customizable. Just add verb "close/closed/closing/closes" should be sufficient.

For me "Issue" is a synonym of "problem" and using this word when talking about a new feature is not correct. The git history have to be precise on each commit.

When i create a new issue (the perfect word would be "ticket") and set the type "Feature". Later when i achieve the code, i push commit as "add feature #123 : short desc message" and i'm expecting the issue #123 to close. "fix issue #123" is not consistent.

Could you add the term "feature" ?

Thanks

Understand. Will think about this...

Implementing this will cause a lot trouble as OneDev has to support this in all places referencing issues (markdown/commit message/title etc) to make the term consistent.

Also when click the "reference issue" button in markdown menu, it will insert "issue #..." in case user does not know the referencing pattern. If this is configurable, OneDev does not what proper term to insert then.

Considering all the problems it causes, I'd like not to change it right now.

We could simply change the term to ticket, and everybody is happy?

As mentioned above. The change is not trivial, and let's just use the same term as GitHub/GitLab.

ok ????