SiT! Bugs

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000303SiT!incidentspublic2008-12-09 16:292011-02-05 14:19
Assigned To 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000303: Incident engineer visibility
DescriptionI feel it would be useful if we could set the visibility on an incident to one of the following:

* Engineer
* Engineer Team (all members of the team)
* System (all users)

With the default to system.

SiT is very open in that all users can see all incidents, though some incidents may relate to potentially sensitive information e.g.:

* HR issues (salary etc) if your using SiT across an institution and not just IT
* Security team/issues you dont want to allow all users to be able to see security issues
TagsNo tags attached.
Attached Files

- Relationships
related to 0001445confirmed Locking an incidents visibility state 
has duplicate 0001437closed Permission Users 
related to 0001401feedback Add permissions to view group incident 

-  Notes
User avatar (0000313)
ivan (administrator)
2008-12-09 16:35

By 'Team' do you mean 'group'?

How would this relate to visibility in the portal? i.e. would an incident marked "Engineer Team (all members of the team)" be visible in the portal or not?
User avatar (0000314)
paulh (administrator)
2008-12-09 16:55

Sorry yes meant group.

The incident would be visible to the user who logged it yes. I'd imagine if you where using sit in this way then you'll have view site incidents turn off in the portal.
User avatar (0002196)
paulh (administrator)
2009-12-03 20:26

Whats the general consensus?
User avatar (0002212)
ivan (administrator)
2009-12-04 10:52

I'm not so keen on hiding things really, but I acknowledge there may be special cases such as those you describe where it might be desirable to limit visibility.

We already have a visibility setting on incident updates, how would this be affected by your suggestion?

Would that be expanded to include Group and Engineer?

I think if we implemented this I'd like to have a permission for it, so that SiT! admins are able to say who can make things private and how private they can make things.
User avatar (0002446)
ivan (administrator)
2010-02-21 21:38

Paul, can you comment further on this so we can decide what to do with it, thanks.
User avatar (0002807)
paulh (administrator)
2010-03-21 18:56

My thoughts where that you would have visibility settings on a per incident basis which would allow either:

* everyone to see (as present)
* only members of your group

This would allow 'secure contents' to be restricted to a group where the members have the relevant access.
User avatar (0002811)
ivan (administrator)
2010-03-21 19:14

How would this relate to the exsting visibility setting? The existing setting relates to contacts, would this be extending that, or be separate to it?
User avatar (0002827)
paulh (administrator)
2010-03-22 12:51

My though is this would be separate, so you'd still have customer visibility as per presently then we would have whole incident visibility which is internal to 'engineers'
User avatar (0002828)
ivan (administrator)
2010-03-22 13:16

Confirming this so long as a permission or config setting is associated with it so that the creation of private incidents can be controlled by an admin.
User avatar (0003540)
kieran (administrator)
2011-01-15 13:57

As an interesting side-effect, we'd need to check during triggers too as an engineer could get emailed every update despite not having the correct permission.

- Issue History
Date Modified Username Field Change
2008-12-09 16:29 paulh New Issue
2008-12-09 16:35 ivan Note Added: 0000313
2008-12-09 16:55 paulh Note Added: 0000314
2009-12-03 20:26 paulh Note Added: 0002196
2009-12-03 20:26 paulh Status new => feedback
2009-12-04 10:52 ivan Note Added: 0002212
2010-02-21 21:38 ivan Note Added: 0002446
2010-03-21 18:56 paulh Note Added: 0002807
2010-03-21 18:56 paulh Status feedback => new
2010-03-21 19:14 ivan Note Added: 0002811
2010-03-22 12:51 paulh Note Added: 0002827
2010-03-22 13:16 ivan Note Added: 0002828
2010-03-22 13:16 ivan Status new => confirmed
2010-03-22 13:16 ivan Summary Incident visibility => Incident engineer visibility
2010-10-16 12:46 paulh Relationship added related to 0001401
2011-01-13 11:24 ivan Relationship added duplicate of 0001437
2011-01-13 11:24 ivan Relationship replaced has duplicate 0001437
2011-01-15 13:57 kieran Note Added: 0003540
2011-02-05 14:19 ivan Relationship added related to 0001445

Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker