Not that I know of. The table’s pagination feature is to navigate through its own pages of loaded data.
You will have to make repeated calls to the Jira REST API using its pagination feature to get all 2,500 attachments, then load all those into the table either all at once or page by page, so that the table contains all 2,500 rows and then the user can paginate through them.
Next, ask yourself the bigger question “Does the user really want or need to see every single attachment in a single, gigantic table, all at once, or do they really only want or need to see smaller, more specific sets of attachments based on different criteria or topics?”
It is really appreciated because I am starting developing and I am a little bit lost.
From your answer, I take it that it is not a good idea to use Dynamic Table to load all the attachments of a project?
Maybe it would be a better idea NOT to use the Dynamic table? And instead, simply list the attachments by user, size and date. And create Previous and Next buttons for pagination.
To answer your question, instead of the user seeing all the attachments in a project, maybe it would be better if the user could filter by date or size, for example.
Could you give me some guidance on this issue?
Thank you very much and I really appreciate your help.
All the questions you asked about different possible scenarios are entirely subjective; it really is up to you to choose which of those scenarios best suits your requirements and the intended behaviour / functionality for your app. My ‘guidance’ will only ever be personal opinion.
I recommend that do some experiments with the different options / methods you’ve described and see which one you visually liked best or found easiest to implement. Then, present a few different versions to your users and get their feedback on which one they liked using and why.