Unknown
opened 3 years ago
-
This is overly complicated, and very error prone. Creating issues via email is mostly for purpose of customer support, and a general type is normally fine, and staff receiving the ticket can change it as necessary.
If one wants to submit issue different from default type, just go ahead to web ui and do it, it is much easier than creating a properties file.
-
Sorry I have limited time, and will not consider features like this just for fun, 😆
-
Previous Value Current Value Open
Closed
-
Yes, of course you can do it in your fork. But it will not be merged into main repository as I don't see any value of it.
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
Watchers (3)
So this has been something I have been thinking about a lot, I love how onedev you do not need to sign in to the web browser and all you need is an email for discussing issues etc.
One issue I have is when submitting issues through email, I can not set the type, priority assignee etc.
I was thinking how this could be implemented, and I got a idea. So when you sign an email you add a signature for people to import your signature, using this concept a specific file such as "issue.properties" could be attached to the email, and selectively detected by onedev, this can then be parsed.
If the configuration file is invalid, the onedev daemon should return an error and point out something, for example:
Type "Robin" does not exist!Only if the email passes all checks, the issues will be created.
This proprieties file can also be used to change issues, such as their type or priority etc. This will mean that email will be almost as powerful as the web frontend, which would be cool (I use the email feature a lot as its more convenient for me)