Updates to handle changes after migrating to Atlasian cloud#174
Updates to handle changes after migrating to Atlasian cloud#174
Conversation
Updated the PX Score handling because the custom field changed when we moved to cloud. Also the tooling that populates it appears not to be working, so I added handling for missing px scores.
Cloud uses account IDs not user IDs. Updated to make it work.
Users are identified by ID not by email address. Updated to handle this.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe pull request refactors Jira assignee handling in the network bugs overview script by introducing a new Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: knobunc The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@knobunc: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The cloud migration renamed the px score custom field and it can now be empty since the bots are not populating it yet.
Cloud uses ids to identify users not email addresses. Changed the code to accommodate.