Issue assignment, issue watchers and issue visibility
Gemini 3.5.4
Our Gemini installation is used by both internal staff and external customers, contractors, etc. We have two visibility settings used for the vast bulk of issues - the default global group "Everyone" and another I defined ("All Internal Staff") which is only visible to, well, all internal staff. All projects have their default issue and comment visibilities set to the latter as a fail-safe way of ensuring that items for internal consumption are not accidentally made visible to everyone.
Recently, an external contractor noticed that an issue that had been assigned to him did not appear in the issue list nor in his "My Work" list. This was because the visibility was set to All Internal Staff, but it did not prevent him accessing the issue through the link on the email notification he received.
There is an inconsistency, however, between the My Work and My Watched Issues lists, as the same issue will appear in the latter list.
In a way, I can understand the issue not appearing in My Work - after all, the attribute is called visibility, not access permissions, and, while it's not preventing access, it is making it invisible! On the other hand, if something is assigned to a user, it's reasonable to expect it to be visible to them (and, inevitably, users won't think to check the visibility setting...). Not having assigned issues appear in the issues listings or issue statistics is misleading.
Could the project issue statistics, issue lists and My Work be made to work more like the My Watched issues list, by including issues outside the user's visibility settings but that are assigned to them?
Cheers,
Nigel.
nharris
· 1 |
|
Wednesday, February 10, 2010, 1:08:02 PM |