View Issue Details

IDProjectCategoryView StatusLast Update
0010831mantisbtadministrationpublic2019-07-06 08:15
Reporterdeatheo Assigned To 
Status acknowledgedResolutionopen 
PlatformxamppOSwindows xp OS Versionsp2
Product Version1.1.8 
Target VersionFixed in Version 
Summary0010831: how can I allow user to view only the issue that assigned to them

as title say
I have already build my mantis system and now I want the user except the administrator can only view the issue that assigned to them, I used to set private to the user but if the user level is the same, and they can also view and edit the issue.Now, I only want user to view the issue that the upper user send to them. How can I do? Can anyone help me about the situation?

TagsNo tags attached.


has duplicate 0022386 closedatrol visibility of the mantis cases 
has duplicate 0022675 closedatrol How to show there own issues only in my view,View Issues pages 
has duplicate 0023342 closedatrol Permission management issue 
has duplicate 0023535 closedatrol how to not see other tkickets that I have assing 
has duplicate 0023536 closedatrol how can I allow user to view only the issue that assigned to them 
related to 0023570 assignedcproensa Implement limit_reporters as a threshold 




2009-10-12 03:34

manager   ~0023134

It is currently only supported to limit reporters to access issues that they have reported. I've seen a couple of requests to allow the same for developers. This may be a feature to consider for 1.3.x. Patches are welcome.



2014-09-26 05:49

reporter   ~0041311

Any Update since 2009? This functionality is really important because some issue must remain private.



2015-07-31 14:36

reporter   ~0051165

Any news on this ticket?
This functionality is very important




2015-08-01 05:41

developer   ~0051166

This functionality is very important

Submitting a patch is always a good idea, as it increases the chances of improvement eventually making it into MantisBT core. All contributions are welcome and greatly appreciated.

Patch submissions can be made in several ways. In the order of preference:

  1. Send us a Pull Request on our Github repository [1]
  2. Attach a GIT patch to the issue
  3. Attach a Unified Diff, clearly specifying the patch's base release

Kindly avoid to upload entire modified PHP files.

Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.




2015-08-01 10:15

reporter   ~0051168

sorry but I am not a specialist in this ... so I do not understand what he wanted me to explain me.


Issue History

Date Modified Username Field Change
2009-08-13 20:41 deatheo New Issue
2009-10-12 03:34 vboctor Note Added: 0023134
2009-10-12 03:34 vboctor Status new => acknowledged
2014-09-26 05:49 anshley Note Added: 0041311
2015-07-31 14:36 gmbasile Note Added: 0051165
2015-08-01 05:41 atrol Note Added: 0051166
2015-08-01 10:15 gmbasile Note Added: 0051168
2017-01-18 14:13 atrol Priority high => normal
2017-01-18 14:13 atrol Severity major => feature
2017-02-15 12:47 atrol Relationship added has duplicate 0022386
2017-04-06 16:53 atrol Relationship added has duplicate 0022675
2017-09-12 04:42 atrol Relationship added related to 0023342
2017-09-12 16:29 atrol Relationship replaced has duplicate 0023342
2017-10-24 14:17 atrol Relationship added has duplicate 0023535
2017-10-24 14:29 altimex Issue cloned: 0023536
2017-11-04 14:03 atrol Relationship added has duplicate 0023536
2019-06-18 06:49 danham File Added: 127.pdf
2019-06-18 07:24 atrol File Deleted: 127.pdf
2019-07-06 08:15 cproensa Relationship added related to 0023570