2500 issues strategy


just curious how you deal with user created issues, duplicates, etc… Many issues on github are dating back to 2015/2016 so probably not relevant anymore.

are there any tools/bots in use today to replay a quite complex business, basically injecting transactions throughout the system, making sure every module gets data in, could be a complex po to delivery and sales flow that should result in a known number, also detecting if presentation/views differ between views, Api and reports, between releases, et’all ?

1 Like

GitHub Issues definitely needs some love. I think the problem is right now the user community is way bigger than the contributing developer community.

If anyone wants to volunteer (and has some reputation on either GitHub or this forum), happy to give the required access.

1 Like