View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0021686mantisbtbugtrackerpublic2016-09-12 02:502017-01-15 23:44
Reportertk Assigned Toatrol  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionduplicate 
Product Version1.3.1 
Summary0021686: Cannot close issues with unresolved child issues
Description

An attempt to close or resolve an issue with unsolved children leads to

APPLICATION ERROR #1104
This issue cannot be resolved until all dependant issues have been resolved.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

without a possibility to override.

In previous installations, accepting the warning issued before the close page was (and should be, at least according to my opinion) sufficient.

I often have to close such kind of issus...

Additional Information

Offening line(s) in bug_update.php:

168 # If resolving or closing, ensure that all dependant issues have been resolved.
169 if( ( $t_resolve_issue || $t_close_issue ) &&
170         !relationship_can_resolve_bug( $f_bug_id )
171 ) {
172         trigger_error( ERROR_BUG_RESOLVE_DEPENDANTS_BLOCKING, ERROR );
173 }

The function relationship_can_resolve_bug() defined in core/relationship_api.php does not refer to any configuration variable which would allow to globally override the block, also.

TagsNo tags attached.

Relationships

duplicate of 0021225 closedcommunity resolving parent issues inconsistency 

Activities

atrol

atrol

2016-09-12 15:17

developer   ~0054009

I often have to close such kind of issus...

Can you give an example where this makes sense?
Isn't it better if you remove the relationship in such a case?
tk

tk

2016-09-13 01:40

reporter   ~0054016

I have issues which generate other issues, but then the major cause for the parent issue is fixed while either the part to be done in the child still is either active, or the main part of the job has moved to the child.
The parent issues are the closed as they otherwise unneccessarily spam the issue list

Anyway, if I /define/ the issue to be resolved in spite of the previous warning I /want/ it to be in that state.
Of course mantis can be designed to insist in correct user behaviour, but then I'd propose at least to introduce a config variable to allow the old workflow by decision of the installing Administrator.
atrol

atrol

2016-09-13 03:33

developer   ~0054018

I am resolving this as a duplicate, to have one place where discussion takes place.
0021225 should also cover your request.
Feel free to reopen if there is a reason to keep this separate.

As a workaround you could use the workflow described in 0021225

  • if done from bug actiongroup: no warning, no error, and the action is performed
tk

tk

2016-09-13 03:42

reporter   ~0054020

actual resolution within 0021225 is sufficent for me