From: Fabian C. <Cen...@in...> - 2008-04-25 07:10:50
|
Hi Is it possible to assign a user to a project so that he can update (add comments) an issue but cannot create a new one? Do I need to create a new access rights level like "UpdaterButNotReporter"? Thanks bye Fabi |
From: Fabian C. <Cen...@in...> - 2008-05-07 11:52:42
|
Hi I recently asked this question but didn't get a reply so I thought I'd send it again with some more information. >Is it possible to assign a user to a project so that he can update >(add comments) an issue but cannot create a new one? Do I need >to create a new access rights level like "UpdaterButNotReporter"? We have several projects where our customers can look into but only one public where they can enter new reports. We did it that way as they most of the time don't know what project a certain bug report belongs to. So they just create all new reports in the same general project and we developers move the reports into the right project. This works out nicely until a feedback from the reporter is required. As the other projects are read-only they can't add new notes. But if I give them updater status they can also enter new reports and change the existing reports which I'd like to prevent. So is there a way to do "half read-only"? Thanks bye Fabi |