Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSβœ” β—Ύ 🚚 Migrated rule - Do you avoid using a single chart when you need it to be scaled? #8255

Merged

Conversation

jeoffreyfischer
Copy link
Member

Tip: Use SSW Rule Writer GPT for help with writing rules πŸ€–

  1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

✏️ Migrated as per SSWConsulting/SSW.Website#1842

  1. What was changed?

✏️ Nothing

  1. Did you do pair or mob programming (list names)?

✏️ I worked with @GordonBeeming, @calumjs and @adamcogan

@jeoffreyfischer jeoffreyfischer self-assigned this Mar 25, 2024
@github-actions github-actions bot added the Age: πŸ₯š - New About 2 hours old label Mar 25, 2024
Copy link
Contributor

github-actions bot commented Mar 25, 2024

PR Metrics

βœ” Thanks for keeping your pull request small.
βœ” Thanks for adding tests.

Lines
Product Code -
Test Code -
Subtotal -
Ignored Code 44
Total 44

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!


**Note:** When rendering a report to your browser or an email, Reporting Services generates a separate image for every single image in the report, even if they are identical. When you are using graphs, images or charts in your report, this can cause a large number of images to be generated. Always include a red warning at the top of any emailed reports so that users do not try and forward or reply to them. Use a warning like this:

<span style="color:red">**Warning:** Do not reply to or forward this report in an email - Outlook may slow down or even hang.</span>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if there is a better way to do this @tiagov8 @bradystroud

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed this with @adam and decided to leave the note - but happy to have other opinions.

@github-actions github-actions bot added Age: 🐣 - Young About 4 hours old Age: πŸ₯ - Adolescent About 8 hours old Age: 🐀 - Mature About 16 hours old and removed Age: πŸ₯š - New About 2 hours old Age: 🐣 - Young About 4 hours old Age: πŸ₯ - Adolescent About 8 hours old labels Mar 25, 2024
@github-actions github-actions bot added Age: πŸ“ - Old About 32 hours old and removed Age: 🐀 - Mature About 16 hours old labels Mar 26, 2024
@jeoffreyfischer jeoffreyfischer merged commit 0672206 into main Mar 26, 2024
5 checks passed
@jeoffreyfischer jeoffreyfischer deleted the migration---avoid-using-single-chart-when-scaled branch March 26, 2024 05:44
@jeoffreyfischer jeoffreyfischer changed the title XSβœ” β—Ύ Migrated rule - Do you avoid using a single chart when you need it to be scaled? XSβœ” β—Ύ 🚚 Migrated rule - Do you avoid using a single chart when you need it to be scaled? Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Age: πŸ“ - Old About 32 hours old
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants