Tiki trackers are great for a bug tracker, as we are dogfooding here.
But what about for a "help desk" setting? -> Private requests from many customers to one company.
Imagine a hosting company. They may have public forums & trackers. But they also have a place where customers can ask direct support requests. And only the customer and the company can follow this tracker.
There is a way for people to just modify their own tracker. But this is more for a user profile, than a series of support requests.
You can also give permission to add a tracker item but not view. But they can't modify existing tracker items. (like sending in a black hole)
If we want people to submit many tracker items, but only see/edit their own, what should we do?
Currently, there is and option "Item creator can modify his items?" at tiki-admin_trackers.php
Maybe we need one: Only item creator can view his items?" Of course, staff working for the company would be admins and could see the trackers for all companies.
Or there could be login drop-down, and only that user can see. Even nicer would be that it's possible for people of the same group to see.
Maybe this possible with the current feature set. In which case, just documentation is necessary.
Some things to experiment:
"My items" in tiki-my_tiki.php
Current workaround is to make a tracker for each customer.
Please see: Issue Tracker
Trackers need "tiki_p_trackers_view_own" permission to view own items only
A profile is needed:
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|