Hello, from the history I see that this error has been reported in February 2015, almost a year ago.
I'm amazed to find out that we are still waiting for a bug fix

Thank you Marty

Hi Baclea,
as per the fix versions, this will be in server release 3.1.0.
If you click the version, it takes you to https://jira.atlassian.com/projects/JSD/versions/56292 where you can watch the release progress.

Thanks,
Marty

Hello,

When a fix will be available for the server JSD?

Thank you,
Mihaela

Hello,

I still having problem with this pagination.

My current version is
+ JIRA Service Desk 3.0.5
+ JIRA Core 7.0.0

PS: previously was on 3.0.0, the only upgrade available is 3.0.5.
Regards,

Yuki

Hello,

Any news about this issue? Thanks.

Regards,
Nicolas.

We are also running into issues relating to this. An ETA or workaround would be greatly appreciated.

Could I get a status update on this? We are testing Jira for a internal ticketing system and if we can get some of these problems resolved we would like to use this as a permanent solution and roll it out to our 60+ sites.

Thank you,
Sean Black

Why does this issue have a label of "fug" ? I had to look it up: "Its not quite a feature and not quite a bug its a fug!"

This absolutely is a bug! How can a Request Participant not being able to page through issues not be a bug?

Hello again,

Today there was a new release but this issue wasn't on the list. What is the criteria for an issue to be solved?
Right now I am using JIRA users licences for my customers so they can access their request, this is not why I bought the Service Desk(unlimited licencese for the customers).

Please solve this issue as soon as possible.

Thank you,
Mihaela

We've recently moved to JSD and this is causing big problems for us as clients can't see tickets that have been raised by others in their team. Please can you give an ETA for a fix?

It's very important for us and our customers. I think, the fix is really easy. Please, fix it ASAP.

Thanks
Radek

Are there updates for this issue?

I had to give access to a client in my Service Desk Project which is not ok. Soon all my clients will figure out this bug and I will have to use licences for jira.

Thank u,
Mihaela

This is very problematic for us. What is the status of addressing this bug?

Support was able to reproduce in my support case sds-6567 before finding and pointing me to this issue.

Hello,

Is there an update for this problem? I use this with all my customers.

Thank u,
Mihaela

Hi owessels,

It seems that the problem occurs if the "Created by me" does not have anything to list on the Page 2. But the "Created by Others" has something to list on the Page 2.

I was able to reproduce the issue on my dev test instance, user has 14 Created by Me and 35 Created by Others. When filtering Open Requests in the Customer Portal, Page 1 (Created by Me = 14) + (Created by Others = first 20) clicking on page 2 (Created by Me = 0) (Create by Others = does not update the list)

Best Regards,
Janice

Hi Janice,

Could you please provide some more information if possible? I have tested this out locally and can't reproduce the problem. The issues need to be indexed to be displayed properly on the My Requests page, so it might be worth seeing if a re-index helps at all.

Cheers,
Oliver Wessels.