fix(Linear Node): Fix issue creation priority (#6813)

This commit is contained in:
Iván Ovejero 2023-08-01 10:58:37 +02:00 committed by GitHub
parent 803b1521fa
commit fce8cc4275
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 6 deletions

View file

@ -2,6 +2,16 @@
This list shows all the versions which include breaking changes and how to upgrade.
## 1.2.0
### What changed?
For the Linear node, priority in issue creation is `4` (previously incorrectly `3`) for `Low`.
### When is action necessary?
If you were using `Low`, you were setting a priority of `Normal`, so please double check you are setting the priority you intend.
## 1.0.0
### What changed?
@ -22,8 +32,8 @@ Update the Node.js version to v18 or above.
This release introduces two irreversible changes:
* The n8n database will use strings instead of numeric values to identify workflows and credentials
* Execution data is split into a separate database table
- The n8n database will use strings instead of numeric values to identify workflows and credentials
- Execution data is split into a separate database table
### When is action necessary?

View file

@ -113,10 +113,9 @@ export const issueFields: INodeProperties[] = [
default: '',
},
{
displayName: 'Priority Name/ID',
displayName: 'Priority',
name: 'priorityId',
type: 'options',
// eslint-disable-next-line n8n-nodes-base/node-param-options-type-unsorted-items
options: [
{
name: 'Urgent',
@ -127,12 +126,12 @@ export const issueFields: INodeProperties[] = [
value: 2,
},
{
name: 'Medium',
name: 'Normal',
value: 3,
},
{
name: 'Low',
value: 3,
value: 4,
},
{
name: 'No Priority',