Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub-departments support #208

Open
ivandiazwm opened this issue May 14, 2018 · 5 comments
Open

Sub-departments support #208

ivandiazwm opened this issue May 14, 2018 · 5 comments
Labels
Projects

Comments

@ivandiazwm
Copy link
Contributor

@ivandiazwm ivandiazwm commented May 14, 2018

No description provided.

@ivandiazwm ivandiazwm changed the title Subdepartments Sub-departments support May 14, 2018
@ivandiazwm ivandiazwm added this to To review in Features May 18, 2018
@ivandiazwm ivandiazwm moved this from To review to Ready for dev in Features May 18, 2018
@ivandiazwm ivandiazwm moved this from Ready for dev to To review in Features May 18, 2018
@ivandiazwm ivandiazwm added the v4.5 label May 18, 2018
@nickbe
Copy link

@nickbe nickbe commented Nov 2, 2018

@ivandiazwm - I'd like to make a small suggestion for this.
I've always have my problems with sub-things. That's why I like you're concept of "Topics and Articles". It seems a minor thing, but it's much easier for people to go along with.

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.

@ivandiazwm
Copy link
Contributor Author

@ivandiazwm ivandiazwm commented Nov 5, 2018

@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 Software Maintenance->License Installation->Request IDE Licence.
In this way you can keep track of common operations. That's the use case we're trying to cover here.
We could use custom tags too, but I think the use case for them would be more similar to the one on github instead of this one.

@nickbe
Copy link

@nickbe nickbe commented Nov 6, 2018

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.

@nickbe
Copy link

@nickbe nickbe commented Mar 14, 2019

I'll admit that sub-departments are basically the right approach.

@IoannisLazaridis
Copy link

@IoannisLazaridis IoannisLazaridis commented Mar 27, 2020

Hello. I would like to know if this feature will be added in the next version. Thank you in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Features
To review
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.