@rombert this should work according 0010969, but it seems you have to set $g_hide_status_default = META_FILTER_NONE; for it 0016889:0039227

I would expect that the test fail.

Got email from rombert, he will check next week

For the record, here is the (confirmed) reason the unit test fails 0022001

This behavior is confirmed in both 1.3.x and master branches.

See PR https://github.com/mantisbt/mantisbt/pull/965 for the fix of the unit test

I think the current behaviour should stay as it is, since it's been long done this way and we risk breaking existing integrations.

There are at least two ways of retrieving all issues:

• setting $g_hide_status_default = META_FILTER_NONE, as @atrol mentioned
• using the the mc_filter_get_issues SOAP API call, which can be backed by a custom filter which returns all issues

Using the mc_filter_search_issues SOAP API call might also work, but I did not check it.

@rquintana, would that work for you?

@rombert, thanks for the feedback.

I agree we should be careful not to break existing applications relying on a behavior of the API.

That being said, the current behavior of mc_project_get_issues() is somewhat confusing, as one's expectation is that it would indeed retrieve all issues (it was apparently also the case for you, since you initially wrote the test script along these lines).

If the decision is the status quo, I would propose that

1. we clearly document the limitation of mc_project_get_issues(), referencing the alternative options you described
2. if really needed, provide a new API mc_project_get_all_issues() that retrieves all issues regardless of $g_hide_status_default setting.

With regards to amending the test script as per your comment [1]

My preference would be for keeping the current behaviour [...] and if we
decide to go for that solution we should adjust the test to pass.

To achieve that, would you recommend that the test takes $g_hide_status_default into consideration ? Or that we just drop the testGetProjectClosedIssues case entirely ?

[1] https://github.com/mantisbt/mantisbt/pull/965#issuecomment-264668132

ping @rombert for

To achieve that, would you recommend that the test takes $g_hide_status_default into consideration ? Or that we just drop the testGetProjectClosedIssues case entirely ?

Thanks for the ping @atrol and sorry for the delay. I had a quick conversation with @dregad about this and here's my take in on the situation

• Backwards compatibility is important to me, and this being an API which is consumed by 3rd party clients any behaviour change would have quite some impact. So I would get the function to take $g_hide_status_default into consideration.
• There's a new API function for searching for issues - the mc_filter_search* functions. Given that, users can perform any kind of searches, not just the predefined ones using mc_filter_get* and mc_project_get* so I don't think we need to add new methods.