Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

[Change Requests] - Creator-only "Edit" action on a declined change request

Open
#4,426 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description
Context

On a declined change request, its creator should get an "Edit" option that takes them to the edit form pre-filled with what they originally proposed, lets them adjust it, and resubmits, instead of rebuilding a new CR by hand. Only the creator sees it, and only when the CR is declined.

Task

Add an "Edit" action to the change request's actions dropdown, shown only to the creator of a declined CR, that routes to the edit project/work-package form pre-filled with the original proposed changes and resubmits through the usual flow.

Acceptance Criteria
  • The "Edit" action appears only when the current user is the CR's creator and the CR was declined.
  • Clicking it opens the edit project/WP form pre-filled with the CR's original proposed changes.
  • The user goes through the normal "why" text step and submits, which calls the resubmit endpoint.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the change request actions dropdown, the existing resubmit endpoint, and the project/work-package edit form and normal “why” step. Trace how declined requests and their original proposed changes are represented; done means the creator alone sees Edit for declined requests, the form is pre-filled, and the normal flow resubmits successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.