Update issue_tracker_manager.py

[sboni-sc]

JIra Watcher Management Improvements

• Enhanced _add_watchers method to prevent duplicate watcher additions. This is essential because if there are a lot of watchers and jira tickets this could amount to a huge load of unnecessary requests when we are updating these tickets for unrelated fields.
• Added error handling for watcher addition failures
• Improved efficiency by checking existing watchers before making API calls

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[sboni-sc]

ptal @jonathanmetzman @vitorguidi

[jonathanmetzman]

/gcbrun

[jonathanmetzman]

Interesting, what are you using this to fuzz?

[jonathanmetzman]

Please run formatter.

[sboni-sc]

Ran formatter on the code: https://github.com/google/clusterfuzz/pull/4788/commits/405f4af7f70b24cc416558fc77950b6c746188b0

We are running this internally for our organization. While we don't have a large volume of tickets, the current approach has been causing issues. Specifically, some of the cron jobs frequently trigger update watcher requests, which result in a significant number of requests being sent to Jira. This high volume of requests is effectively contributing to the overwhelming of Jira, leading to it being locked for updates and writes.

[jonathanmetzman]

/gcbrun

[github-actions[bot]]

This pull request has not had any activity for 60 days and will be automatically closed in two weeks

[jonathanmetzman]

/gbcurn

[jonathanmetzman]

Sorry I was on paternity leave.

[github-actions[bot]]

This pull request has not had any activity for 60 days and will be automatically closed in two weeks

[github-actions[bot]]

Automatically closing stale pull request