#0825 separating issues from specific users
Hi,
I would like to try to implement a shared help desk model and I can't find a method try to pull this off within the documentation. I also tried to search for this, please forgive me if I missed a previous example.
My goal is to allow several separate groups to share a single help desk and segment the issues so that the help desk can see every issue, but the end users can only see this issues appropriate their particular group.
Company A|
Company B|
Company C|----->support staff
Company D|
Company E|
I think I could do this with separate instances, but then the support staff would only be able to login to each instance one at a time. such as:
http://issues.company.com/company_a
http://issues.company.com/company_b
http://issues.company.com/company_c
http://issues.company.com/company_d
http://issues.company.com/company_e
I would like to provide a single url to every team and control what they see and can update via their user ID. So ideally a URL like:
http://issues.company.com
Could I achieve my objective using domains? If so how? or is there a better way to implement this?
Thanks!
-Richard
12 months old
Okay, so a ton of digging over the weekend and I found the solution. The term within this product is called a join-in issue tracker. I was able to create several dummy issue trackers for testing and so long as my user-id and password were the same in the master issue tracker as they were in the subordinate issue tracker then everything worked like a charm.
Please close my ticket for me!
Hi Richard - Im trying to simulate exactly this functionality and youre solution is amazing - however I am not sure I understood what you meant by the "so long as my user-id and password were the same in the master issue tracker as they were in the subordinate issue tracker then everything worked like a charm" - do you mean I need to re-create all the users from sub-ordinate issue trackers in the master issuetracker as well?
Richard: Well spotted with the join-in feature. Clearly it's not documented well enough if you had to struggle to find it.
Turbanator: No need to duplicate any userid/password combinations. Take Richard's set up and set up company_a, company_b, company_c, company_d, company_e and create an issuetracker, on the same level, called all_companies. Now, join-in company_a-e in all_companies. Lastly, for security. You set up the user who's accessing all_companies in the parent of all these 6 issuetrackers (a-e and all_companies) and then set up individual users inside each company issuetracker.