vinu1998 you assigned the ticket to plugins that seem unrelated to the issue you are reporting.
By assigning the ticket to three unrelated plugins, changes-since-last-success-plugin, ui-samples-plugin, and update-sites-manager-plugin, you involved maintainers for those plugins. Jira chose to assign the issue to the first plugin listed. Tony correctly asked why you believe that the changes-since-last-success-plugin is involved in the issue.
I ask the same question about the other two plugins you mentioned. If you are using the ui-samples-plugin, you should remove it. It shows UI samples and provides no other benefits to Jenkins users. I doubt that you are using the updates-sites-manager-plugin either.
An issue report to an open source project like Jenkins is an attempt to persuade people to give you their time. You're not paying them. Your claim on their time is only as strong as your ability to persuade them that your issue should receive some of their time.
One way of being more likely to persuade others to help you is to provide the details that are listed in "How to report an issue". The details requested there are especially important for cases like this one where you seem to be seeing a very general failure. With 290 000 Jenkins installations around the world, it is quite rare to see a very general failure. That usually means you need to provide many details that will help people understand why your situation is different enough to see this failure when other users do not see it.
Hi vinu1998
I'm a little unsure why you think this is attributable to the changes-since-last-success plugin and have assigned to me?
Do you have a sequence of actions to reproduce this issue and a specific configuration?