Quin
opened 3 years ago
-
This is simply because my current invoices can only go as far down as "Tasks", which either means creating a new task for every issue on OneDev (which just isn't manageable), or grouping them by Department, i.e., frontend, backend, sysadmin, etc. And there really isn't a great way to break it down, other than displaying every single timeslip (which requires adding comments to each timeslip too, all more-or-less saying the same thing).
There isn't an option to set hourly rates for each of the developers, only at a project or task level (so it would mean even more highly specific tasks).
-
Standalone plugin can be copied into OneDev installation to improve its functionality.
For your case, I think custom plugin does help too much. Maybe custom issue field of numeric type can help, and then you can add pipeline jobs to run periocially or run as required to query issues using RESTful api and do some statistics/calcuation. You can use any language you like in the pipeline to achieve this.
-
For your case, I think custom plugin does help too much
Typo: For your case, I think custom plugin does NOT help too much
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Minor
|
| Assignee |
Not assigned
|
Howdy
I am looking at developing a plugin for OneDev. It's a fairly simple idea where it syncs my accounting software to OneDev, as they share a lot of the same data (Clients, Projects, Tasks). I was going to make my own platform to handle all this, but that would simply create another dataset to maintain.
Aside from the languages used (I'm happy to learn new languages), are there any real limitations? How would a standalone plugin work/look like? Are there any features in the pipeline I should be aware of?
My plugin idea is timetracking for the tasks/issues (as I bill hourly), being able to set hourly rates for the other developers (different roles/skillsets/experience), and then POSTing to the accountancy software to create an invoice. I'd implement timeslips which would be marked as "billed" when invoiced, and they would be separate from the Issues (we'd only be using the reference really, i.e. "#1166 - Developing custom plugins").
I think on the Issue, I'd have it pulls all the timeslips relating to it in order to see "total time spent" as an addition to project management.