licenser / orgtool2 Goto Github PK

Unit log:

• for member assignments (who by whome + position)
• for member left (who by whome + position)
• ship assign (what by whome)
• ship removed (what by whome)

Member logs

• for rewards (what by whome)

Contracts

• creation time (by whome)

One log table per event group (i.e. unit_user_logs), this allows automatic tracking and validation. Additional data bout the event (i.e. join/leave, date)

API wise items can be assigned to units the same way users can, would be nice to allow this :)

Users should be able to delete themself.

I have not relibably been able to reproduce this but switching to 'items' in the item/category/template tab too quickly can crash the frontend with a message that a render in progress can't be destroyed.

A quick option to give all or no permissions to a user on per group and global level

mockup:

It would be nice to see in the item list what items are assigned to a unit and which are not

Add 'default/active' permission.

if active is set a user can perform actions on themselfs (i.e. a basic this user was approved by an admin permission)

We could use this to show the 'you are nota activates' page

• add config option to the ui
• check for ui elements
• check on requests for 40*'s

When editing something and making changes and then pressing X or cancle a dialoge about 'do you want to discard your changes' would be nice.

The concrete case where I ran into it was:

• open a item
• assign a unit
• then close the window

This was not saving the unit even so the unit was listed which lead to some confusion, so having a window about 'discard' would be neat.

Move to a 'mark as deleted' policy instead of deleting objects from the database. It's a change invisible for the FE but allows never invalidate references. This will be helpful for #20.

When in https://org.nautilus.group/#/players/x/stats where x = the player number.

The drop down menus are covered by the other fields so that you can only see certain options. I can produce more screenshots upon request.

It would be wonderful if ships could be assigned (reassigned) the same way members can be assigned. Dragging them on the unit you want them in.

When in the overview it's currently impossible to find out what ships are in a unit, just which types are there.

When editing a user from the list that is not the logged in user the user is not read, this leads to permissions not being read. This means permissions can't be edited for other users.

See: 69e04b7

Right now items/templates/categories are all under the same url it would be nice to have them seperated.

when a user has the 'active' permissiojn then can edit their player even if they don't have player edit permission. That way non admin users can edit themselfs.

The big question is how do unit owners handle permissions?

• What permissions does a unit leader have?
• What permissions does an officer have?
• Do they propagate? Down?

If we say, include a item in a unit we not only need to check the permissions on the /unit endpoint but also on the /item endpoint.

@skoma is this still a thing what does should it log? Are server logs (we have those) enough or do is it application logs? What's the goal of this?

@skoma Is this still a thing?