View Issue Details

IDProjectCategoryView StatusLast Update
0019667mantisbtotherpublic2015-05-11 11:17
Reporterkburkum Assigned Toatrol  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformHosted InstanceOSWindowsOS Version7
Summary0019667: Application Error 0000401 When Clicking View Issues Menu
Description

The following system error is generated when I click the View Issues option on the left navigation menu.

APPLICATION ERROR 0000401
Database query failed. Error received from database was #1066: Not unique table/alias: 'mantis_custom_field_string_table_11' for the query: SELECT Count( DISTINCT mantis_bug_table.id ) as idcnt FROM mantis_bug_table JOIN mantis_project_table ON mantis_project_table.id = mantis_bug_table.project_id LEFT JOIN mantis_custom_field_string_table mantis_custom_field_string_table_11 ON mantis_bug_table.id = mantis_custom_field_string_table_11.bug_id AND mantis_custom_field_string_table_11.field_id = 11 LEFT JOIN mantis_custom_field_string_table mantis_custom_field_string_table_11 ON
mantis_bug_table.id = mantis_custom_field_string_table_11.bug_id AND mantis_custom_field_string_table_11.field_id = 11 WHERE mantis_project_table.enabled = ? AND ( mantis_bug_table.project_id = 22 ) AND ( ( mantis_bug_table.status in (?, ?, ?, ?, ?, ?) ) AND (mantis_custom_field_string_table_11.value = ?) ) .
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.

Steps To Reproduce

1) Open https://agileframeworks.mantishub.com

2) Select the "Project Change Requests" project

3) Click the View Issues menu on the left navigation

Additional Information

The above error does not happen if I try the same actions on a different project.

TagsNo tags attached.
Attached Files
Error.jpg (193,757 bytes)   
Error.jpg (193,757 bytes)   

Relationships

related to 0019670 closedvboctor View Issues page fails when a custom field is used for filtering and sorting 

Activities

kburkum

kburkum

2015-04-27 11:06

reporter   ~0050634

Note:

The crossed out 0000401 in the Summary and Description fields were entered (copied / pasted) as:

"number sign"401

kburkum

kburkum

2015-04-27 11:11

reporter   ~0050635

Update: I have had two others in our organization that use this same hosted instance try the above and they do NOT receive the error. Seems to be localized to me. Tried logging out and refreshing my cache. No luck with that.

atrol

atrol

2015-04-27 14:31

developer   ~0050637

kburkum,

This is not a bug or feature request for MantisBT (you are describing problems with MantisHub ). I am therefore resolving this issue as "no change required".

Please contact the MantisHub support for it.

Feel free to reopen the issue, if you are able to reproduce the issue using a standard MantisBT.

atrol

atrol

2015-04-27 14:32

developer   ~0050638

Reminder sent to: vboctor

mantis_custom_field_string_table_11?
It seems you changed the code to use customer specific table names.

vboctor

vboctor

2015-04-27 21:19

manager   ~0050640

@atrol, I don't recall implementing such change. Do you have a specific checkin to provide context?

vboctor

vboctor

2015-04-27 23:04

manager   ~0050641

@atrol, I read the issue more carefully and noticed that it is a MantisHub issue hence the assumption that I made such change. This is not a schema issue, but the code that generates the query has a bug in mantisbt code which appends the custom field id to table name in two locations in the filter_api.

I've created 0019670 to track the MantisBT bug.

@kburkum - you have submitted a support ticket in MantisHub, I will respond to that to make sure you are not blocked.

atrol

atrol

2015-04-28 00:28

developer   ~0050647

Sorry @vboctor for closing this one, I wasn't aware that there is a change since 1.2.9
https://github.com/mantisbt/mantisbt/commit/170e9397540ea39e0519aa842aba02ef9309a5d9#diff-1ab8336d4a0a80eee673bc4863607041

That's why I thought it must be a MantisHub issue.

vboctor

vboctor

2015-04-28 01:44

manager   ~0050648

No worries @atrol. Anyway, l've addressed your comment on the pull request and will get the fix in soon for the rc1 release.

kburkum

kburkum

2015-04-28 12:17

reporter   ~0050672

I was provided a URL query string by vboctor and this resolved my issue on the MantisHub side of things.