Hi Ryan-

I looked into this issue and was unable to recreate it. The tasks returned are the tasks that are associated to the service_request that was requested.

Is there any additional information you can provide such as the dates that seemed incorrect? There are a couple of dates here (service request date, task updated/created at/delivered on date) that could be of help.

Thank you

Hi Ryan-

I tested Euwe as well as master. Is it possible to get more information about the timestamps?

Thanks!

Hey Yoder,

After taking a look at your appliance, I do not see any irrelevant tasks. I have also looked closely at the API code and ran some separate tests to ensure that the correct tasks are being returned, and I have not been able to reproduce any problems.

Happy to take a look if you think you encounter this again - screenshots and exact tasks would be helpful for debugging.

Thanks!
- Jillian

Hi Ryan,

Apologies for the delay. Yes, please put something on my calendar so that we can go through the issue together.

Thanks!
- Jillian

Hi Ryan--

was it possible to get the JSON response of the actual tasks? In particular, 

https://cfme.test.kent.edu/api/service_requests/1000000000174/tasks?expand=resources

and 

https://cfme.test.kent.edu/api/service_requests/1000000000174/request_tasks?expand=resources

Thanks!

Hi Ryan--

I no longer need that information as I found the root cause of the problem.

Here is a PR that explains the issue:
https://github.com/ManageIQ/manageiq/pull/15265

Essentially, `/request_tasks` is the API call that should be made and the `/tasks` request should be avoided.

What is happening is the `/tasks` is pretty much configured incorrectly, so when you get the hrefs back, they are referencing a different object than the actual tasks that are associated with the service requests.

Thanks!!

Updated PR: https://github.com/ManageIQ/manageiq/pull/15357

Verified that "request_tasks" is returned instead of "tasks" and that "tasks" is redirected to "request_tasks" when "tasks" subcollection is accessed.

GET /api/service_requests/1/tasks/1
{
    "href": "https://<addr>/api/service_requests/1/request_tasks/1",
    ...

GET /api/service_requests/1/tasks
{
    "name": "request_tasks",
    ...
    "resources": [
        {
            "href": "https://<addr>/api/service_requests/1/request_tasks/1"
        }
    ...

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0380