Understanding the Jira Filter issues

[Swaroop]

I have come across a strange issue with Jira filter with a subtle shuffling of jira bugs in which the bug sequence of a few jiras gets changed and that goes unnoticed. However, after compiling the entire filter bugs you realise that few bug has been documented twice and you end up missing documenting the few jiras. Is it a known pattern or somebody else has also encountered it anytime? 

[Rebekka Heilmann (viadee)]

Hello @Swaroop and welcome to the Community,

i absolutely cannot follow you. What do you mean by "few jiras". Jira is the product name and doesn't refer to any specific Object/Configuration/Feature within the product.

Could you maybe provide some screenshots to clarify?

[Swaroop]

Hi Rebekka, Thanks for responding. 

Sorry, i couldn't be clear enough. Let me create the entire scenario for you. 

I work on documenting periodic release notes. For every bug the engineering team creates a jira ticket (in short we casually refer them to a Jira). I hope i have simplified it. 

Now, for an instance, i have received a filter with over 100 Jira tickets and while documenting them one by one i have observed that there is a subtle change of sequence in the list of jira tickets. It is so subtle that it cannot be detected with just only 4-5 tickets exchanging their positions. And it is not practical to remember all tickets and detect its duplication untill the final doc is generated and cross-verified. 

So, technically my question revolves around the same. Is this behavior of jump/change in the sequence is usual/normal? 

Am i doing something wrong? (I am not changing any settings through-out the project time. The page remains open on the browser till the entire list is documented)

I understand its a bit weird situation as it has happened more than a couple of times.

Thanks again.