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

Tweaks for Organisation Units #1052

Closed
baszoetekouw opened this issue Nov 7, 2023 · 2 comments
Closed

Tweaks for Organisation Units #1052

baszoetekouw opened this issue Nov 7, 2023 · 2 comments
Labels
discuss Needs to be discussed; do not implement as is.
Milestone

Comments

@baszoetekouw
Copy link
Member

baszoetekouw commented Nov 7, 2023

  • Conceptually:
    • Should a Org manager with one or more Units enabled maybe be called a Unit Manager instead? That would make the distinction between an Org Manager with Units and an Org Manger without Units much more clear. --> voor nu ok, probably solved by other UI tweaks. Maybe adjust if pilot users find it confusing.
  • In Org admin.manager overview:
    • In table of admins/managers, show units the manager is responsible for (or "all"/empty/*)
    • Unclear that you can click on a manager to adjust unit roles
  • In Org Manager edit screen:
    • "CO's to be managed" -> "Units to be managed" (??) fixed
    • "All CO's" -> "All units" (??) etc fixed
  • Authorisations:
    • unclear how this works: if a manager can only manage a specific unit, are they then allow to manage COs without unit?
      • ah: seems that if a CO has no Unit, all managers can manage theat CO (regardless of Unit of Manager). If CO has a Unit, only Unit Managers can manage it.
      • Is this what we expect? Shouldn't the default be that a manager can manage no Units rather than all Units?
    • make clear for Org Manager which Units they can manage. --> no quick fix, let's wait for questions from actual users.
    • Should Unit Managers be able to see (read-only) COs of other Units? Currently, they can't, but that's confusing, because it is unclear to those managers that they don't have a full view of the Org. --> no, minimal disclosure
    • An Org Manager can create COs without units (shouldn't be possible) --> fixed
  • CO screen:
    • use – (–) instead of - (hyphen or hyphen-minus) in title of CO to separate Org and Unit fixed in 2dc8a5c
    • In edit, move "Relevant unit" to below "Responsible Organisation" fixed
    • In edit, make clear that "Relevant Unit" is coupled to "Responsible Organisation" --> order is changed
  • API:
@baszoetekouw baszoetekouw added the discuss Needs to be discussed; do not implement as is. label Nov 7, 2023
@baszoetekouw baszoetekouw mentioned this issue Nov 7, 2023
14 tasks
FlorisFokkinga added a commit that referenced this issue Nov 13, 2023
baszoetekouw pushed a commit that referenced this issue Nov 15, 2023
@FlorisFokkinga FlorisFokkinga moved this from New to In progress in SRAM development Nov 20, 2023
@baszoetekouw
Copy link
Member Author

Mostly done, continues in #1264 #1265 #1266

@sram-project-automation sram-project-automation bot moved this from In progress to To be tested in SRAM development Feb 25, 2024
@baszoetekouw baszoetekouw added this to the v32 milestone Mar 11, 2024
@mrvanes mrvanes moved this from To be tested to Being tested in SRAM development Mar 11, 2024
@mrvanes
Copy link
Contributor

mrvanes commented Mar 11, 2024

#1264 (comment)

@mrvanes mrvanes moved this from Being tested to Todo in SRAM development Mar 12, 2024
@baszoetekouw baszoetekouw moved this from Todo to To be deployed in SRAM development Mar 12, 2024
@sram-deploy-tools-automation sram-deploy-tools-automation bot moved this from To be deployed to Done in SRAM development Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Needs to be discussed; do not implement as is.
Projects
Archived in project
Development

No branches or pull requests

3 participants