Quin
opened 4 years ago
-
Name Previous Value Current Value Type
Improvement
Support Request
-
@Quin452 Thanks for the suggestion. Will show that service desk email in project.
As to long email address for child projects, I thought of using project id, but that's less meaningful. With project path in email address, user can know which project the support request is going to.
Also please let me know if you have any issues pushing repo to OneDev, or any other problems using it.
-
Hi
Yes, I understand the reasoning, but is there a way to group projects without it being a child project?
Ideally, I want my clients to simply use support+projectname, and not support+Clients/BusinessName/projectname, as that will make things more confusing for them.
Is there a way around this, either with separate grouping or using email aliases? -
How about specifying the service desk email of a project as part of project setting?
-
This setting is not available yet. If this approach is acceptable, I will create an improvement request for it.
-
@robin that would be perfect. I can keep the projects grouped to where they need to be (under Clients) and then I can give a custom email address (or in this instance, just support+projectName) to the clients for their support.
I am happy with everything else with the Service Desk (the reply-to, the issue number).
-
Filed as issue #576. You may watch to get notified.
-
Previous Value Current Value Open
Closed
-
Closing this support request. Feel free to file other issues if there are problems using OneDev.
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
Not assigned
|
Hi
I've got OneDev installed and I'm starting to play around with things. I come from a Gitlab environment, so it's a bit of a learning curve. The documents could do with updating, and being more clear.
Just pushing the repos up to OneDev was an issue, as well as getting the Service Desk to work (an external resource, that uses both images and text to give the information; it was easy to miss what was in the arrow bubbles).
Tangent aside, one thing I have found to be a bit lacking is how the Service Desk works with child projects. From my testing, you need to use
+[parentProject]/[childProject]@for child projects, and I daren't imagine how far down it goes.To give some context, I could end up with
support+Clients/Business-Name/Project-Name@, which is a mouthful, and yet this is the only way I can see to organise the projects.It would also be nice to have a URL/Mailto to view/copy within the project (as I had to figure this out myself when it came to child projects).