View Issue Details

IDProjectCategoryView StatusLast Update
0004352mantisbtbugtrackerpublic2004-08-29 01:48
Reporterbpfennig Assigned Tothraxisp  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionduplicate 
Product Version0.19.0a2 
Fixed in Version0.19.0rc1 
Summary0004352: Resolve button should have own access rights
Description

I've added an additional status on my local installation. After bugfix the developer have to set this new status (to be tested). This is the signal for our testers to test the bugfix. Now the testers (updaters) should set the bug to resolved, but the resolve button are not visible for updaters.

I have to change the "handle_bug_threshold" to UPDATERS, then the resolve button is visible for our updaters, but now they are also shown in the "assigned to" list.

The resolve button should have it's own access rights.

TagsNo tags attached.

Relationships

duplicate of 0003772 closedthraxisp Status updating should be different from bug updating 

Activities

Wanderer

Wanderer

2004-08-18 10:16

developer   ~0007055

Well, in current CVS-HEAD statuses work in slightly diffeent manner
I think, you missed custom resolved status feature (or there aren't such thing in a2??). Anyway, this problem solved in HEAD, you can see it in action in my demo-site http://bts.e-city.net.ru/demo/ (use reporter/reporter, updater/updater, developer/developer pairs for login)
Issue resolved to "Verify wait", after it it can be changed only into "Verify fail" or "Resolved" statuses
And changing status controlled by separate variable, thus - user, which can update status doesn't became "possible handler" in project