View Issue Details

IDProjectCategoryView StatusLast Update
0009139mantisbtbugtrackerpublic2018-05-01 00:28
Reporterlgsolano Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Summary0009139: resolution values dont depend on status values. they should
Description

as of 1.1.1 resolutions have no workflow.
as a result, you can set any resolution value any time, regardless of the status.

resolution changes should be conditioned by status changes.

Tagsmantishub

Relationships

related to 0016054 new Refactoring the notion of "fixed issue" 
has duplicate 0016793 closedatrol Resolution should be dependent on Status 
has duplicate 0008940 closedatrol Some resolutions shouldn't be available when status is set to Closed 
has duplicate 0005686 closedatrol Resolutions of OPEN and REOPENED should not be allowed when resolving or closing an issue. 
has duplicate 0023510 closedatrol resolution field 

Activities

sandyj

sandyj

2017-10-05 15:11

reporter   ~0057899

It seems that a relationship between status and resolution fields already exists. Our testing shows that in some cases 'invalid' resolution and status return error number 24. So this issue seems like a bug rather than a feature request.

According to our testing, when manually editing the issue details and attempting to change the status or resolution fields to a 'dis-allowed' combination the error is returned and also when using the change status button and actively changing the status (i.e. not leaving the defaulted setting) the error is returned. However, when using the change status button and leaving the defaulted resolution value, it does not check for a valid resolution.

The expectation is that 'open' or 're-openned' status should return an error when in resolved or closed state. All other resolution values are only compatible with 'resolved' or 'closed' and should return an error.