Bug Description
PRs/MRs created today incorrectly display "Updated PR" (or "Updated Merge Request" for GitLab)
instead of "Made PR" in the scrum report.
Root Cause
Two bugs in scrumHelper.js (lines 1768 and 1775):
-
Wrong property case: The code checked item.State (capital S), but both APIs
return lowercase state:
-
Wrong state value for GitLab: The GitLab branch also compared against 'open',
but GitLab uses 'opened' for open merge requests. The mapGitLabItem() function
normalizes this for issues (line 272/342) but passes through the raw state for MRs,
so the comparison must use 'opened' in the GitLab code path.
Steps to Reproduce
- Create a new PR today on any repository
- Generate scrum report with "Yesterday" timeframe
- The PR shows "Updated PR" instead of "Made PR"
Expected Behavior
| Scenario |
Before |
After |
| GitHub PR created today |
"Updated PR" ❌ |
"Made PR" ✅ |
| GitLab MR created today |
"Updated Merge Request" ❌ |
"Made Merge Request" ✅ |
Screenshots
Additional Context
Add any other context about the problem here.
Contribution Checklist
Bug Description
PRs/MRs created today incorrectly display "Updated PR" (or "Updated Merge Request" for GitLab)
instead of "Made PR" in the scrum report.
Root Cause
Two bugs in
scrumHelper.js(lines 1768 and 1775):Wrong property case: The code checked
item.State(capital S), but both APIsreturn lowercase
state:statereturnsopen,closed, orallstatereturnsopened,closed,locked, ormergedWrong state value for GitLab: The GitLab branch also compared against
'open',but GitLab uses
'opened'for open merge requests. ThemapGitLabItem()functionnormalizes this for issues (line 272/342) but passes through the raw state for MRs,
so the comparison must use
'opened'in the GitLab code path.Steps to Reproduce
Expected Behavior
Screenshots
Additional Context
Add any other context about the problem here.
Contribution Checklist