Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
@ivandiazwm - I'd like to make a small suggestion for this.
So maybe it would be a good idea to replace sub-departments with "contexts". I think this also reflects more the way a ticket/issue/bug tracker works. There's a department and then there are contexts per department. This would also fit right into the current access system because the departments remain the angle point for the access rights.
@nickbe What do you mean by context? kind of like tags or a second-depth sub-department?
The intention of this task it to create a tree of departments. It that sense, when you select a department it shows the list of children and so on. I think the use case for this is when you handle common tasks request through a support system.
For example, let's say you have an IT/maintenance area in a company and they handle request by an internal ticket system and they are responsible of buying software licenses, hardware, fix computers, install software. If you need, for example, a software license for an IDE, you would create a ticket in the department
For me a department is how you define the structural units of an organisations employees. While a context can be a anything virtual or abstract. Like in your exemple: "Software Maintenance (Department) -> New Software Licsenses (Context).
Also I think it's very important not to have a tree with more than levels (Departments, Contexts). More depth seems too complicated for my taste.
What I suggest is simply the following solution: Have a tree with 2 levels and then let the admin name the level as he wish. That way you can name them "department/sub-department" as well as having any other structural description.
But I really would keep the access rights to the top level node only. Even if a complex access system seems interesting it would also overcomplicate the general handling.