Garret Wassermann

Thanks for the report! Many sites like even GitHub use the ticket ID right in the URL, I think it can be helpful to easily share the URL and verify...

I can see the case where sorting by most recently updated might be useful too, sort of an activity stream. Sorting by priority could be an option too. I wonder...

Ah ok, if we're trying to sort by several parameters at once, that is more complex. Datatables might be able to handle that but I haven't investigated yet.

version 0.3 should be coming soon so will have to re-evaluate if these concerns still exist in next version. I think 0.3 got a number of significant user/group management upgrades.

The 0.3 release is out now, do these issues still apply?

There is no github workflow yet. I have manually updated the ReadTheDocs config in the past, I forgot to point to 0.4 when it came out although it's not hugely...

Thanks, that document looks useful. I'll tag this for the next release as something to set up before it gets released.

Yes I think this could be good though I'm not sure how easy it is for python to check only the new emails when making tickets. Will have to investigate.

Permissions need an overhaul so might need to look at this alongside #239 for the next release. Sorry about the inconvenience, but please continue to use the workaround of going...

@Mte90 I suspect this might have actually been fixed already, I think I remember updating code to check for staff and not superusers at one point. We'll need to doublecheck.