View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0012851mantisbtbugtrackerpublic2011-03-11 04:482023-04-28 14:06
Reportermark_tseng Assigned Todregad  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version1.2.4 
Summary0012851: developer report a problem, why updater can do edit the probelm?
Description

1.If developer report a problem.
2.Select View Status to private.
3.Why updater can do edit the problem?
4.Cancel the updater of the markers on the "update an issue" in Workflow Thresholds.
5.The problem still exists.
6.But if select View Status to public.
7.The problem did not happened.

TagsNo tags attached.

Activities

atrol

atrol

2011-03-11 05:07

developer   ~0028399

did you change $g_private_bug_threshold ?
mark_tseng

mark_tseng

2011-03-13 21:14

reporter   ~0028409

Last edited: 2011-03-13 21:14

Yes, but problem still exist..
atrol

atrol

2011-03-14 03:47

developer   ~0028410

I am wondering that your updater user is able to view the issue.
Without changing $g_private_bug_threshold updaters are not able to view private issues. (default setting is developer)
mark_tseng

mark_tseng

2011-03-14 04:15

reporter   ~0028411

No, updater users can not see the issue, when $ g_private_bug_threshold (View private issues) setting to developer.

i would like updater users only see the issue but does not edit the issue.

Thanks for your help.
atrol

atrol

2011-03-14 04:23

developer   ~0028412

Use "Manage" -> "Manage Configuration" -> "Workflow Thresholds"
Disable the checkbox in column "updater", row "Update an issue"
mark_tseng

mark_tseng

2011-03-14 04:51

reporter   ~0028414

Yes, I've to disable the checkbox in column"updater", row "Update an issue".
But it can not resolve my question...

If the bug is updater report(View Status:private), this option is useful

ButIf the bug is developer report(View Status:private), this option is useless
dregad

dregad

2023-04-17 05:07

developer   ~0067663

Without activity for so many years, I assume this is no longer an issue.