fix(jira): remove unnecessary projectId dependency from manualIssueKey#3547
Conversation
Issue keys are self-sufficient identifiers in Jira (e.g., PROJ-123). The manualIssueKey field is a text input where users type the key directly, so it should not depend on projectId/manualProjectId. This dependency caused the field to clear unnecessarily when the project selection changed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview This prevents a manually entered issue key (e.g., Written by Cursor Bugbot for commit 84b3c58. Configure here. |
Greptile SummaryThis PR makes a targeted one-line fix to the Jira block configuration: the
Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[User selects Operation\ne.g. read / update / delete] --> B{Mode?}
B -- basic --> C[issueKey selector\ndependsOn: credential, domain, projectId]
B -- advanced --> D[manualIssueKey short-input\ndependsOn: credential, domain]
C --> E{projectId set?}
E -- No --> F[Field blocked / disabled]
E -- Yes --> G[Fetch issues list for project]
G --> H[User picks issue from list]
D --> I{credential + domain set?}
I -- No --> J[Field blocked / disabled]
I -- Yes --> K[User types issue key directly\ne.g. PROJ-123]
H --> L[Execute Jira operation]
K --> L
style D fill:#c8e6c9,stroke:#388e3c
style K fill:#c8e6c9,stroke:#388e3c
Last reviewed commit: 84b3c58 |
Summary
projectIdandmanualProjectIdfrom themanualIssueKeyfield'sdependsOnin the Jira blockPROJ-123) are self-sufficient identifiers — no project selection needed when typing them directlyTest plan