iDempiere Instead of Github

[Binary Statistics]

Hi, is anyone successfully developing software with iDempiere as their issue tracker? I saw

https://groups.google.com/g/idempiere/c/gTN3VauJfn8/m/j1yToihHAgAJ

so it seems it's possible through requests. Does anyone have any comments about this? I don't need to migrate to iDempiere from Github, I'm starting fresh. Trying to weigh up the pros and cons of using iDempiere for this.

[Anozi Mada]

Why not use specialized software for that? something like redmine or openproject that works out of the box.

Regards,

Anozi Mada

[Norbert Bede]

hi, we have 2 effort on that.

1. github to idempiere backend plugin => syncing issues beetween github as name says and idempiere special modules - sponsored by cloudempiere developed by Alan - not public yet, need more tuning.

2. we are using requests as support tickets,  knowledge base base as documentation and contact activities as timesheets.  (see some screenshot bellow)

Both projects frontend developed in Angular with SSR - and huge time investigation and many missing features against complex systems - BUG they are doing we are mostly required and make our processes fluent.

the main reason why we went by this really hard way, is learn, improve idempiere rest, and i had fed-up from jira because being too complex, redmine never used.

still you can develop it easier, eg. by jsp portal if you are experienced with java.

Norbert

[Binary Statistics]

Hi Anozi,

The main point of using iDempiere for this task, to have one system for everything if at all possible. I have realised that generally, this doesn't work very well and you're still better off using specialised tool for every unique task. Unless you're prepared to spend the necessary time as Norbert has done. But I figured that an issue tracker should be such a simple thing, that surely iDempiere is capable of doing this as well. I'm already using MS Project, which as far as I'm aware doesn't have an issue tracker type functionality, so Redmine and OpenProject would mean either migration which I don't want to do or playing around with interfaces/integration, which I don't want to do either. I want something that works out of the box.

Hi Norbert,

Thanks! Yes learning something new is always fun, and the benefits of doing something custom that works perfectly to a T for your use case, makes the whole process much more worthwhile. Some food for thought for sure from your response!

[Norbert Bede]

hi,

iDempiere is not specialised for PSA. https://en.wikipedia.org/wiki/Professional_services_automation - possible but lot of work - we did some effort with less/more success.

Out-of-box you can try idemepiere jsp e-commerce here - https://test.idempiere.org/wstore/index.jsp login with gardenworld users. you can enter and/or comment requests - as result you can see "tickets" in idempiere internally. 

Norbert

[Binary Statistics]

Thanks Norbert, wasn't even aware of PSA. A lot of things are much clearer now for me. Still need to read a bit more to fully understand things but I'm now much better acquainted with why iDempiere does what it does and why I wasn't able to get it to play nice in some of it's use cases!

[Carlos Antonio Ruiz Gomez]

Hi,

I would like to add that the Requests feature of iDempiere is very capable to manage the basics of PSA, a big advantage is that is integrated into iDempiere so invoicing is just one click

In an old project our client managed a basic HelpDesk with the help of the old webstore, and the backend worked in iDempiere.

However, two things:

- at this moment there is not a good customer oriented interface, the old webstore still works, but the design is ugly, it requires some work to make it fancy and maybe a security audit as is based in old technology

You can test the old webstore at https://test.idempiere.org/wstore/index.jsp

Login with -> admin @ gardenworld.com  (you must keep the spaces before and after the @)

and password GardenAdmin

A customer can add requests here -> https://test.idempiere.org/wstore/request.jsp

and then they can be processed in the backend

the further interaction with customer is also managed there, for example -> https://test.idempiere.org/wstore/requests_sr.jsp

- ideally using REST could be possible to create a customer oriented interface, responsive

The basic functionality is very simple:

** create a new request  (like this)

** query my open requests  (like this other this)

** update requests (and ability to attach files, like this)

(Would be great if somebody could contribute a software like this)

With that you have a very basic feature to communicate with customers and manage their tickets.

Now, internally Requests have some interesting features like basic workflows, notifications, escalation, and of course, all the things that you can do with iDempiere (ad-hoc reporting and querying, attachments, trigger workflows, translations, email notifications, etc)

Also the Kanban dashboard plugin can be configured to manage requests, or the geolocation plugin.

The thing is, if that's what is required I would thing there are advantages to do it in iDempiere.

But, there would be maybe some fancy features missing, like markdown formatting, embedding images, complex workflows - then maybe other specialized software can be better.

Regards,

Carlos Ruiz

El 31/5/22 a las 15:05, Binary Statistics escribió:

[Binary Statistics]

Hi Carlos,

Thanks for the additional info.

I won't be able to contribute this particular improvement. I don't have a need for a customer facing interface.