Skip to content

Friendlier per-owner subtasks #34

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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

jeannamatthews
Copy link
Collaborator

No description provided.

@jeannamatthews jeannamatthews changed the title Jmatthews/new asana reports Friendlier per-owner subtasks Aug 9, 2025
@jeannamatthews jeannamatthews self-assigned this Aug 9, 2025
@jeannamatthews jeannamatthews requested a review from nshuba August 9, 2025 20:45
Copy link
Collaborator

@nshuba nshuba left a comment

Choose a reason for hiding this comment

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

Thanks for doing this! I left some comments - but nothing major really, so I won't block approving.

@nshuba nshuba self-requested a review August 13, 2025 17:26
@jeannamatthews
Copy link
Collaborator Author

jeannamatthews commented Aug 15, 2025

@nshuba in the postmortem you mentioned wanting to have another look at things checked in since you reviewed. Let me know if there is anything else you'd like me to do on this before merging.

Copy link
Collaborator

@nshuba nshuba left a comment

Choose a reason for hiding this comment

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

Looks good. Please fix the part where we might assign the same pixel to multiple people, the rest is minor. Feel free to merge after that.

Comment on lines +52 to +54
pixelPhrase += `

New to these reports ? See <a href="${INSTRUCTIONS_TASK_URL}">View task</a>`;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Would this not work with Asana APIs?

Suggested change
pixelPhrase += `
New to these reports ? See <a href="${INSTRUCTIONS_TASK_URL}">View task</a>`;
pixelPhrase += `\nNew to these reports ? See <a href="${INSTRUCTIONS_TASK_URL}">View task</a>`;


// Write thisOwnersPixelsWithErrors to a temporary file
const tempFilePath = path.join(dirPath, `pixel_errors_${owner}.json`);
fs.writeFileSync(tempFilePath, JSON.stringify(ownersPixelData, null, 2));
Copy link
Collaborator

Choose a reason for hiding this comment

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

Minor: our prettier standard is 4 spaces

if (pixel.owners) {
pixel.owners.forEach((owner) => ownersSet.add(owner));
pixel.owners.forEach((owner) => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Won't this assign the same pixel more than once if there are multiple owners? I'd just assign to the first owner. Otherwise we risk 2+ people spending their time fixing the same thing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants