Create BZ checklist for all issues with new feature label.

[JmillsExpensify]

We should be creating regression tests for all issues, no matter whether they are a bug or a new feature. Accordingly, let's ensure that the BZ checklist for new feature even though we aren't today.

This is an internal issue though creating in App for visibility.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01632f7d35826f4e94
• Upwork Job ID: 1703983742829371392
• Last Price Increase: 2023-09-19

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01632f7d35826f4e94

[melvin-bot]

Triggered auto assignment to @garrettmknight (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @aimane-chnaif (Internal)

[garrettmknight]

Handling in the Expensify/Expensify issue.

[garrettmknight]

Still working through the E/E issue - will leave this one open to test the update with.

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@flodnv] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[flodnv]

Was just testing 👍

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@flodnv] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@flodnv] The PR that introduced the bug has been identified. Link to the PR:
• [@flodnv] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@flodnv] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@flodnv] Determine if we should create a regression test for this bug.
• [@flodnv] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[garrettmknight]

E/E issue is where we're working on this. This issue is open for testing. Will close it when the E/E issue closes.

[flodnv]

New comment was posted here #28831 (comment)