Multiple Managers for a User

Discuss problems installing or using TrackStudio.

Multiple Managers for a User

Postby jdshilling » Thu Aug 07, 2003 11:46 pm

Hi,

We are just setting up TrackStudio and things are going well.
We think we have a good understanding of how to set up projects.
We set up our projects by department, eg. Projects > Dept> All Dept Projects.

But we have some questions on how to set up users.
Some Users have child users, eg manager and developer.
Sometimes the developers need to have access to other managers projects.
We can't seem to find a way to do this.
If we put the developer under their manager only their manager can give them accesss to a project. Which makes some sense, but the way we set up our projects, a manager only has access to his projects, not the other managers projects.

How should we proceed?
Should we give managers access to all Projects their staff may ever work on.

Ideally, users would be able to be assigned to multiple managers.

Thanks for any ideas you have.

Jeff
jdshilling
 
Posts: 1
Joined: Thu Aug 07, 2003 11:16 pm

Postby mvasenkov » Fri Aug 08, 2003 12:52 am

Well, TrackStudio is a hierarchical issue tracking system :) , so to add a developer (child user) of manager A into a project of manager B, any of this managers, A or B should ask his own manager C, who had access to upper-level project (issue). This manager C should add the developer to ACL of project (you need) in 'access control' tab.
Skype (RU): max.vasenkov
Email/Jabber: max.vasenkov@gmail.com
twitter: @winzard
mvasenkov
TrackStudio Support
 
Posts: 374
Joined: Tue Jan 14, 2003 5:57 pm
Location: Smolensk

In addition

Postby mvasenkov » Fri Aug 08, 2003 12:57 am

In addition, manager A can create an issue like 'Need to add developers Peter and John to a project 'JHD'' and set handler to his own manager.
Skype (RU): max.vasenkov
Email/Jabber: max.vasenkov@gmail.com
twitter: @winzard
mvasenkov
TrackStudio Support
 
Posts: 374
Joined: Tue Jan 14, 2003 5:57 pm
Location: Smolensk

Re: Multiple Managers for a User

Postby admin » Fri Aug 08, 2003 11:38 am

jdshilling wrote:Hi,

We are just setting up TrackStudio and things are going well.
We think we have a good understanding of how to set up projects.
We set up our projects by department, eg. Projects > Dept> All Dept Projects.

But we have some questions on how to set up users.
Some Users have child users, eg manager and developer.
Sometimes the developers need to have access to other managers projects.
We can't seem to find a way to do this.
If we put the developer under their manager only their manager can give them accesss to a project. Which makes some sense, but the way we set up our projects, a manager only has access to his projects, not the other managers projects.

How should we proceed?
Should we give managers access to all Projects their staff may ever work on.

Ideally, users would be able to be assigned to multiple managers.

Thanks for any ideas you have.

Jeff


I think you need matrix project management, that can be implemented very easy with TrackStudio :-)

User Management tab used to describe organizational breakdown structure (OBS). For example, you should define it like this (3-level strucutre):
Code: Select all
                              ROOT
-----------------------------------------------------------
           R&D           QA              VP of PM
      department     department     
       manager          manager
---------------------------------------------------------------
       dev1 dev2      qa1 qa2 qa3       pm1 pm2


Suppose, also, you have 2 projects in 3-level hierarchy:
Code: Select all
      ROOT
---------------------------
     projects
---------------------------
prj1           prj2


Now you (root) should give access control to the "projects" to all department managers (development,qa and pm).

Its all :-)

1) VP of PM can assign managers to projects
2) Managers of concrete project can ask QA or R&D manager about required testers and developers for their project
3) QA and R&D managers can assign testers and developers to projects and revoke them

Please note, that QA manager, for example, can generate money report for all testers in all projects, but can't get imformation about developers.
Project manager of some project can't get information about other projects. Root can get all information.

This simple structure can be extended, so you can create additional level in user hierarchy (by region location, for example) and in task hierarchy (by customer) with responsible managers for each region and customer.

About you question: if developer need access to another manager's project - project manager of that project should create request (via TrackStudio) to R&D dep. manager and R&D dep. manager should assign developer to that project.

So, users actually can be assigned to multiple managers:
- their assigned to manager of deparment (via user hierarchy functionality)
- their assigned to one or more project manager/projects (via access control functionality).
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 8143
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia


Return to TrackStudio Support

Who is online

Users browsing this forum: No registered users and 8 guests

cron