forcedotcom / forcedotcom/git2gus
`defaultBuild` config does not support previous builds
Open
USER STORY
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In `.git2gus/config.json` if the `defaultBuild` option is not set to the most recent build, no Gus work item is created when the Gus creation label is added.
Here is our previous config that was silently failing to create a new Gus work item when `BUG P2` is added to a Github Issue:
```
{
"productTag": "",
"defaultBuild": "222"
}
```
Here is the new config that successfully creates work items:
```
{
"productTag": "",
"defaultBuild": "224"
}
```
Even on an older `defaultBuild`, work items should be created and targeted to that release.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.