Concepts - Users, Roles, Designations, Managers & Teams
Users are at the core of UpRaise. Although completely integrated with JIRA, UpRaise needs to create its own entries in the database for Users and their attributes. This data is then utilised in UpRaise to segment users into groups based on different attributes.
Users who are deactivated or deleted from JIRA will be automatically updated within UpRaise. Since these users cannot login in JIRA anyway, we don't provide an option to remove them from UpRaise.
Each one of the users in UpRaise Company Directory will either hold a role or will have 'no access' to UpRaise. At any given time, one user can have only one role.
Do keep in mind that Role defined under UpRaise company directory is limited for UpRaise features, it won't have any bearing on JIRA features or features of any other addon.
Designation is an attribute associated with each UpRaise user. One user can have only one designation at a time. By default, UpRaise comes with HR Manager, Product Manager, Project Manager, QA Engineer, Software Developer designations. Obviously, this list can be easily managed to better match your organisation needs. This is an optional attribute. User can very well exist in UpRaise without a designation.
Manager is someone to whom a given user reports to. To make Jon Doe manager of Jane Doe, both of them must already exist as UpRaise users. One UpRaise user can have only one manager associated. This is an optional attribute. User can very well exist in UpRaise without a manager.
Team is a grouping of users based on their functional areas or organisational strategy. Teams in UpRaise are a special entity which act as containers for users. One team can have one team lead & multiple UpRaise users as team members. Any given team can have an associated parent team. This allows UpRaise to create an org hierarchy chart to better help you visualise things.
There is an additional attribute called team level. It lets you treat any team as a group. By using levels, you can create multi-level hierarchy for example Department -> Division -> Team -> Sub-team. In essence, UpRaise will treat everything as a Team, whether they are a department or a division or something else will depend on what level in the hierarchy they exist.
Note that one UpRaise user can be a part of more than one team.
Team lead is a special type of team member. There are configurations across modules that give special permissions to team leads such as being able to create team level OKRs for the team they are leading.
UpRaise will be further enhanced so that team leads have additional permissions such as managing their own team, creating review forms for them etc.