You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MrRefactoring opened this issue
May 1, 2024
· 0 comments
Labels
questionRaised for inquiries, clarifications, or discussions related to the project.wontfixIndicates that, while acknowledged, the particular issue or request won't be acted upon.
Is there a guide on how to migrate from jira.js version 2.19.1 to 3.0.5? After updating the version and running my project, I encounter several errors related to bad requests and incorrect project specifications. Here are some of the errors I'm seeing:
Error indicating that the project must be specified to create a version.
Error stating that the version name is not valid.
Error updating issue with a 404 not found due to a null URI.
Below is an example of how I'm currently using jira.js:
constclient2=newVersion2Client({host: process.env.RM_JIRA_URI,newErrorHandling: true,telemetry: false,rejectUnauthorized: false,authentication: {basic: {username: process.env.RM_JIRA_USERNAME,password: process.env.RM_JIRA_PASSWORD}}})asyncfunctionisVersionInProjectNew(fixVersion,projectToCheck){constproject={projectIdOrKey: projectToCheck}constversions=awaitclient2.projectVersions.getProjectVersions(project).then(res=>{if(res.errorMessages&&res.errorMessages.length>=0){throwres}returnres}).catch(error=>{logger.error('failed to load isVersionInProject',error)return[]})letversionsForFixVersion=[]if(versions){versionsForFixVersion=versions.filter(v=>v.name===fixVersion).map(v=>{logger.info('Fixversion '+fixVersion+' exists in project: '+projectToCheck+' - '+v.description+'.')returnv})}returnversionsForFixVersion.length>0}
Could anyone provide insights or documentation on proper migration steps?
Thanks!
The text was updated successfully, but these errors were encountered:
MrRefactoring
added
bug
Indicates a reported issue or malfunction that needs fixing.
Investigation required
Points out issues that need further exploration or detailed examination.
question
Raised for inquiries, clarifications, or discussions related to the project.
wontfix
Indicates that, while acknowledged, the particular issue or request won't be acted upon.
and removed
bug
Indicates a reported issue or malfunction that needs fixing.
Investigation required
Points out issues that need further exploration or detailed examination.
labels
May 1, 2024
questionRaised for inquiries, clarifications, or discussions related to the project.wontfixIndicates that, while acknowledged, the particular issue or request won't be acted upon.
Hi,
Is there a guide on how to migrate from jira.js version 2.19.1 to 3.0.5? After updating the version and running my project, I encounter several errors related to bad requests and incorrect project specifications. Here are some of the errors I'm seeing:
Below is an example of how I'm currently using jira.js:
Could anyone provide insights or documentation on proper migration steps?
Thanks!
The text was updated successfully, but these errors were encountered: