Repo specific settings ended up in global settings.json
Issue #312
open
I have multiple customers with multiple projects. Each with some combination of bitbucket, Jira, github and gitlab.
Therefor I have configured the Atlassian plugin on a per workspace settings. It irks me to find the following in my global settings.json. It seems to me this belongs in a Workspace Jira.
"atlascode.jira.jqlList": [
{
"id": "xxxx-xx-xxx-xxx-xxx",
"enabled": true,
"name": "Project Name",
"query": "assignee = currentUser() ORDER BY lastViewed DESC ",
"siteId": "xxxx-xx-xxx-xxx-xxx",
"monitor": true
}
],
Comments (3)
-
-
- changed status to open
-
- changed component to Misc
- Log in to comment
@Roland van Laar , once you’ve chosen to save settings to the workspace any changes made will be saved to the workspace. It’s possible that this setting was written to the global settings before you made the change to save the settings locally. If you make changes to a JQL query are those changes saved at the global level or at the workspace level?